... | ... | @@ -23,7 +23,7 @@ Changes to attachments should be given in the CR, after any changes to the prose |
|
|
>
|
|
|
> **--- SECOND CHANGE (LI-PS-PDU.ASN) ---**
|
|
|
>
|
|
|
> { changes}
|
|
|
> { changes}
|
|
|
>
|
|
|
> **--- END OF CHANGES ---**
|
|
|
|
... | ... | @@ -42,6 +42,8 @@ The CR author obtains a standard diff file that describes the changes to each at |
|
|
|
|
|
The diff file will contain a set of changes to all the attachments affected by the CR. The CR author can then take the set of changes for each attachment and put them in a change block for that attachment. An example is given below:
|
|
|
|
|
|
![image](uploads/0eaee10451dce68d3175b4d82bffb41c/image.png)
|
|
|
|
|
|
### Showing changes to attachments via track changes
|
|
|
|
|
|
The CR author can obtain the changes in Word track-changes format by downloading the post-build artefacts from the Merge Request front page.
|
... | ... | |