rtems/rtems-docs
1
0
Fork 0
mirror of https://git.rtems.org/rtems-docs/ synced 2025-07-06 04:02:09 +08:00
Code Issues Packages Projects Releases Wiki Activity

coding-gen-patch:Convert TBD to rest Format(GCI 2018)

Browse Source
This commit is contained in:
Pritish Jain 2018-12-01 14:57:48 +05:30 committed by Joel Sherrill
parent 8059b68d21
commit 65476b44a5
1 changed files with 27 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
eng/coding-gen-patch.rst
View File

@ -6,5 +6,30 @@
Generating a Tools Patch
************************
TBD - Convert the following to Rest and insert into this file
TBD - https://devel.rtems.org/wiki/Developer/Coding/GenerateAPatch
.. COMMENT:TBD - Convert the following to Rest and insert into this file
.. COMMENT:TBD - https://devel.rtems.org/wiki/Developer/Coding/GenerateAPatch
The RTEMS patches to the development tools are generated using a command like this
.. code block:: shell
diff -N -P -r -c TOOL-original-image TOOL-with-changes >PATCHFILE
where the options are:
* -N and -P take care of adding and removing files (be careful not to
include junk files like file.mybackup)
* -r tells diff to recurse through subdirectories
* -c is a context diff (easy to read for humans)
* -u is a unified diff (easy for patch to apply)
Please look at the generated PATCHFILE and make sure it does not contain
anything you did not intend to send to the maintainers. It is easy to
accidentally leave a backup file in the modified source tree or have a
spurious change that should not be in the PATCHFILE.
If you end up with the entire contents of a file in the patch and can't
figure out why, you may have different CR/LF scheme in the two source
files. The GNU open-source packages usually have UNIX style CR/LF. If
you edit on a Windows platform, the line terminators may have been
transformed by the editor into Windows style.