Difference between revisions of "Simple Patch"
From GnuCash
(First draft, RFC) |
m (→Requirements: Make "macOS" consistent with Apple branding.) |
||
Line 5: | Line 5: | ||
* The program diff, which is part of several packages: | * The program diff, which is part of several packages: | ||
** '''Linux:''' diffutils, | ** '''Linux:''' diffutils, | ||
− | ** ''' | + | ** '''macOS:''' XCode [?], |
** '''Windows:''' MinGW [part of the GnuCash Package?]. | ** '''Windows:''' MinGW [part of the GnuCash Package?]. | ||
* Optional a program to search recursivly for strings in files like ''grep'' to find the right file. | * Optional a program to search recursivly for strings in files like ''grep'' to find the right file. | ||
+ | |||
==Procedere== | ==Procedere== | ||
# Locate the file with the typo e.g. with <tt>grep</tt>. | # Locate the file with the typo e.g. with <tt>grep</tt>. |
Latest revision as of 20:17, 4 July 2020
Purpose of this page is to show, how to create a simple patch without the hazzle to set up a developement environment. This should allow normal users to send a patch for a typo in a text file.
Requirements
- Any editor for plain text. That means specific for Windows users use Notepad instead of Word.
- The program diff, which is part of several packages:
- Linux: diffutils,
- macOS: XCode [?],
- Windows: MinGW [part of the GnuCash Package?].
- Optional a program to search recursivly for strings in files like grep to find the right file.
Procedere
- Locate the file with the typo e.g. with grep.
- Note
- The next 2 steps might need administrator rights.
- Create a backup of the file: copy <filename>.<suffix> <filename>.bak
- Edit the original file with a plain text editor.
- Test the new version in its application.
- Create a patch:
diff -u <filename>.bak <filename>.<suffix> ><filename>.patch
- Create a bugreport at https://bugs.gnucash.org
- Attach <filename>.patch to your bugreport