<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/Documentation/git-format-patch.txt, branch v2.7.3</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.7.3</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.7.3'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2016-02-05T22:54:09Z</updated>
<entry>
<title>Merge branch 'dw/signoff-doc' into maint</title>
<updated>2016-02-05T22:54:09Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2016-02-05T22:54:09Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=7aae9ba6613c38d9f275955af80881fb67ddbd8a'/>
<id>urn:sha1:7aae9ba6613c38d9f275955af80881fb67ddbd8a</id>
<content type='text'>
The documentation has been updated to hint the connection between
the '--signoff' option and DCO.

* dw/signoff-doc:
  Expand documentation describing --signoff
</content>
</entry>
<entry>
<title>Expand documentation describing --signoff</title>
<updated>2016-01-05T21:42:39Z</updated>
<author>
<name>David A. Wheeler</name>
<email>dwheeler@dwheeler.com</email>
</author>
<published>2016-01-05T19:20:26Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=b2c150d3aa82f6583b9aadfecc5f8fa1c74aca09'/>
<id>urn:sha1:b2c150d3aa82f6583b9aadfecc5f8fa1c74aca09</id>
<content type='text'>
Modify various document (man page) files to explain
in more detail what --signoff means.

This was inspired by https://lwn.net/Articles/669976/ where
paulj noted, "adding [the] '-s' argument to [a] git commit
doesn't really mean you have even heard of the DCO...".
Extending git's documentation will make it easier to argue
that developers understood --signoff when they use it.

Signed-off-by: David A. Wheeler &lt;dwheeler@dwheeler.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>format-patch: add an option to suppress commit hash</title>
<updated>2015-12-15T18:03:40Z</updated>
<author>
<name>brian m. carlson</name>
<email>sandals@crustytoothpaste.net</email>
</author>
<published>2015-12-15T01:52:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=3a30aa17879b08f96262abb9a22c7bbe8f56e4c9'/>
<id>urn:sha1:3a30aa17879b08f96262abb9a22c7bbe8f56e4c9</id>
<content type='text'>
Oftentimes, patches created by git format-patch will be stored in
version control or compared with diff.  In these cases, two otherwise
identical patches can have different commit hashes, leading to diff
noise.  Teach git format-patch a --zero-commit option that instead
produces an all-zero hash to avoid this diff noise.

Signed-off-by: brian m. carlson &lt;sandals@crustytoothpaste.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'po/doc-branch-desc'</title>
<updated>2015-09-17T19:29:03Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2015-09-17T19:29:03Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=a2654356d4ef9ffac4adda2b053d45def8e0a45c'/>
<id>urn:sha1:a2654356d4ef9ffac4adda2b053d45def8e0a45c</id>
<content type='text'>
The branch descriptions that are set with "git branch --edit-description"
option were used in many places but they weren't clearly documented.

* po/doc-branch-desc:
  doc: show usage of branch description
</content>
</entry>
<entry>
<title>doc: show usage of branch description</title>
<updated>2015-09-14T19:50:33Z</updated>
<author>
<name>Philip Oakley</name>
<email>philipoakley@iee.org</email>
</author>
<published>2015-09-14T14:10:53Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=561d2b7934caaa5e0917979da82ca59b17a4e5f9'/>
<id>urn:sha1:561d2b7934caaa5e0917979da82ca59b17a4e5f9</id>
<content type='text'>
The branch description will be included in 'git format-patch
--cover-letter' and in 'git pull-request' emails. It can also
be used in the automatic merge message. Tell the reader.

While here, clarify that the description may be a multi-line
explanation of the purpose of the branch's patch series.

Signed-off-by: Philip Oakley &lt;philipoakley@iee.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'fk/doc-format-patch-vn'</title>
<updated>2015-06-24T19:21:56Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2015-06-24T19:21:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=61461791be23618c52df7f81975228dea47e64d3'/>
<id>urn:sha1:61461791be23618c52df7f81975228dea47e64d3</id>
<content type='text'>
Docfix.

* fk/doc-format-patch-vn:
  doc: format-patch: fix typo
</content>
</entry>
<entry>
<title>doc: format-patch: fix typo</title>
<updated>2015-06-10T21:37:04Z</updated>
<author>
<name>Frans Klaver</name>
<email>fransklaver@gmail.com</email>
</author>
<published>2015-06-10T21:01:14Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d614f0754927c6f4c265014e205f0d1d5b7c856b'/>
<id>urn:sha1:d614f0754927c6f4c265014e205f0d1d5b7c856b</id>
<content type='text'>
reroll count documentation states that v&lt;n&gt; will be pretended to the
filename. Judging by the examples that should have been 'prepended'.

Signed-off-by: Frans Klaver &lt;fransklaver@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>*config.txt: stick to camelCase naming convention</title>
<updated>2015-03-14T05:13:46Z</updated>
<author>
<name>Nguyễn Thái Ngọc Duy</name>
<email>pclouds@gmail.com</email>
</author>
<published>2015-03-11T20:32:45Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=da0005b8853137c91e44867d899910d5c7eb4425'/>
<id>urn:sha1:da0005b8853137c91e44867d899910d5c7eb4425</id>
<content type='text'>
This should improve readability. Compare "thislongname" and
"thisLongName". The following keys are left in unchanged. We can
decide what to do with them later.

 - am.keepcr
 - core.autocrlf .safecrlf .trustctime
 - diff.dirstat .noprefix
 - gitcvs.usecrlfattr
 - gui.blamehistoryctx .trustmtime
 - pull.twohead
 - receive.autogc
 - sendemail.signedoffbycc .smtpsslcertpath .suppresscc

Helped-by: Eric Sunshine &lt;sunshine@sunshineco.com&gt;
Signed-off-by: Nguyễn Thái Ngọc Duy &lt;pclouds@gmail.com&gt;
Signed-off-by: Eric Sunshine &lt;sunshine@sunshineco.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>format-patch: add "--signature-file=&lt;file&gt;" option</title>
<updated>2014-05-27T19:38:32Z</updated>
<author>
<name>Jeremiah Mahler</name>
<email>jmmahler@gmail.com</email>
</author>
<published>2014-05-24T04:08:14Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=7022650f61ff7d7c9297db4a04f4e93ae14e1750'/>
<id>urn:sha1:7022650f61ff7d7c9297db4a04f4e93ae14e1750</id>
<content type='text'>
Add an option to format-patch for reading a signature from a file.

  $ git format-patch -1 --signature-file=$HOME/.signature

The config variable `format.signaturefile` can also be used to make
this the default.

  $ git config format.signaturefile $HOME/.signature

  $ git format-patch -1

Signed-off-by: Jeremiah Mahler &lt;jmmahler@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>format-patch doc: Thunderbird wraps lines unless mailnews.wraplength=0</title>
<updated>2013-10-14T23:20:01Z</updated>
<author>
<name>Ramsay Jones</name>
<email>ramsay@ramsay1.demon.co.uk</email>
</author>
<published>2013-10-06T20:51:31Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=f737684d34215f029376f65770c401c2d2b24fe4'/>
<id>urn:sha1:f737684d34215f029376f65770c401c2d2b24fe4</id>
<content type='text'>
The Thunderbird section of the 'MUA-specific hints' contains three
different approaches to setting up the mail client to leave patch
emails unmolested. The second approach (configuration) has a step
missing when configuring the composition window not to wrap. In
particular, the "mailnews.wraplength" configuration variable needs
to be set to zero. Update the documentation to add the missing
setting.

Signed-off-by: Ramsay Jones &lt;ramsay@ramsay1.demon.co.uk&gt;
Signed-off-by: Jonathan Nieder &lt;jrnieder@gmail.com&gt;
</content>
</entry>
</feed>
