user/sven/git.git/Documentation/git-format-patch.txt, branch v1.7.7.4

Document negated forms of format-patch --to --cc --add-headers

2011-08-29T22:27:07Z

The negated forms introduced in c426003 (format-patch: add --no-cc, --no-to, and --no-add-headers, 2010-03-07) were not documented anywhere. Add them to the descriptions of the positive forms. Signed-off-by: Thomas Rast Signed-off-by: Junio C Hamano

Merge branch 'jn/format-patch-doc'

2011-05-04T22:51:41Z

* jn/format-patch-doc: Documentation/format-patch: suggest Toggle Word Wrap add-on for Thunderbird Documentation: publicize hints for sending patches with GMail Documentation: publicize KMail hints for sending patches inline Documentation: hints for sending patches inline with Thunderbird Documentation: explain how to check for patch corruption

Merge branch 'jn/maint-format-patch-doc'

2011-05-04T22:51:31Z

* jn/maint-format-patch-doc: Documentation: describe the format of messages with inline patches

Documentation/format-patch: suggest Toggle Word Wrap add-on for Thunderbird

2011-04-19T18:31:39Z

Of the (now) three methods to send unmangled patches using Thunderbird, this method is listed first because it provides a single-click on-demand option rather than a permanent change of configuration like the other two methods. Signed-off-by: Johannes Sixt Signed-off-by: Junio C Hamano

Documentation: publicize hints for sending patches with GMail

2011-04-15T20:28:03Z

The hints in SubmittingPatches about stopping GMail from clobbering patches are widely useful both as examples of "git send-email" and "git imap-send" usage. Move the documentation to the appropriate places. While at it, don't encourage storing passwords in config files. Signed-off-by: Jonathan Nieder Signed-off-by: Junio C Hamano

Documentation: publicize KMail hints for sending patches inline

2011-04-15T20:28:03Z

These hints are in git's private SubmittingPatches document but a wider audience might be interested. Move them to the "git format-patch" manpage. I'm not sure what gotchas these hints are meant to work around. They might be completely false. Signed-off-by: Jonathan Nieder Signed-off-by: Junio C Hamano

Documentation: hints for sending patches inline with Thunderbird

2011-04-15T20:28:03Z

The standard reference for this information is the article "Plain text e-mail - Thunderbird#Completely_plain_email" at kb.mozillazine.org, but the hints hidden away in git's SubmittingPatches file are more complete. Move them to the "git format-patch" manual so they can be installed with git and read by a wide audience. While at it, make some tweaks: - update "Approach #1" so it might work with Thunderbird 3; - remove ancient version numbers from the descriptions of both approaches so current readers might have more reason to complain if they don't work. Signed-off-by: Jonathan Nieder Signed-off-by: Junio C Hamano

Documentation: explain how to check for patch corruption

2011-04-15T20:28:03Z

SubmittingPatches has some excellent advice about how to check a patch for corruption before sending it off. Move it to the format-patch manual so it can be installed with git's documentation for use by people not necessarily interested in the git project's practices. Signed-off-by: Jonathan Nieder Signed-off-by: Junio C Hamano

Merge v1.7.5-rc2 into jn/format-patch-doc

2011-04-15T20:27:04Z

This is to sync with the recent updates in Documentation/SubmittingPatches and Documentation/format-patch.txt

Documentation: describe the format of messages with inline patches

2011-04-15T20:24:53Z

Add a DISCUSSION section to the "git format-patch" manual to encourage people to send patches in a form that can be applied by "git am" automatically. There are two such forms: 1. The default form in which most metadata goes in the mail header and the message body starts with the patch description; 2. The snipsnip form in which a message starts with pertinent discussion and ends with a patch after a "scissors" mark. The example requires QP encoding in the "Subject:" header intended for the mailer to give the reader a chance to reflect on that, rather than being startled by it later. By contrast, in-body "From:" and "Subject:" lines should be human-readable and not QP encoded. Inspired-by: Jim Meyering Signed-off-by: Jonathan Nieder Improved-by: Junio C Hamano Improved-by: Drew Northup Signed-off-by: Junio C Hamano