Changeset 65476b4 in rtems-docs


Ignore:
Timestamp:
Dec 1, 2018, 9:27:48 AM (5 months ago)
Author:
Pritish Jain <pritishjain2001@…>
Branches:
master
Children:
0184167
Parents:
8059b68
git-author:
Pritish Jain <pritishjain2001@…> (12/01/18 09:27:48)
git-committer:
Joel Sherrill <joel@…> (12/18/18 00:45:49)
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • eng/coding-gen-patch.rst

    r8059b68 r65476b4  
    77************************
    88
    9 TBD - Convert the following to Rest and insert into this file
    10 TBD - https://devel.rtems.org/wiki/Developer/Coding/GenerateAPatch
     9.. COMMENT:TBD - Convert the following to Rest and insert into this file
     10.. COMMENT:TBD - https://devel.rtems.org/wiki/Developer/Coding/GenerateAPatch
     11
     12The RTEMS patches to the development tools are generated using a command like this
     13
     14.. code block:: shell
     15  diff -N -P -r -c TOOL-original-image TOOL-with-changes >PATCHFILE
     16
     17where the options are:
     18
     19* -N and -P take care of adding and removing files (be careful not to
     20include junk files like file.mybackup)
     21
     22* -r tells diff to recurse through subdirectories
     23* -c is a context diff (easy to read for humans)
     24* -u is a unified diff (easy for patch to apply)
     25
     26Please look at the generated PATCHFILE and make sure it does not contain
     27anything you did not intend to send to the maintainers. It is easy to
     28accidentally leave a backup file in the modified source tree or have a
     29spurious change that should not be in the PATCHFILE.
     30
     31If you end up with the entire contents of a file in the patch and can't
     32figure out why, you may have different CR/LF scheme in the two source
     33files. The GNU open-source packages usually have UNIX style CR/LF. If
     34you edit on a Windows platform, the line terminators may have been
     35transformed by the editor into Windows style.
Note: See TracChangeset for help on using the changeset viewer.