source: rtems-docs/eng/coding-gen-patch.rst @ 1fdd3cf

5
Last change on this file since 1fdd3cf was e52906b, checked in by Sebastian Huber <sebastian.huber@…>, on 01/09/19 at 15:14:06

Simplify SPDX-License-Identifier comment

  • Property mode set to 100644
File size: 1.3 KB
Line 
1.. SPDX-License-Identifier: CC-BY-SA-4.0
2
3.. Copyright (C) 2018.
4.. COMMENT: RTEMS Foundation, The RTEMS Documentation Project
5
6Generating a Tools Patch
7************************
8
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 TracBrowser for help on using the repository browser.