Patches which change existing code are read by people as well as the 'patch' program. They benefit from the following two tricks:
Use -w to remove diffs that are only whitespace (indents) changes. Makes diffs much easier to read. Use -U5 to get 5-line context rather than the default 3-line context. This tends to make a sequence of edits appear as one long set of changes. On Wed, Jun 15, 2011 at 2:49 PM, Ted Dunning <[email protected]> wrote: > git diff --no-prefix > > That produces a patch more like what SVN does. > > On Tue, Jun 14, 2011 at 10:10 PM, Sergey Bartunov <[email protected]>wrote: > >> Hello. I'm going to commit something (especially command-line utils >> for sequential HMM) to "train" in commiting patches. >> Does the Jira accept git patches? Or I have to create ones from subversion >> only? >> > -- Lance Norskog [email protected]
