From: Dennis Stosberg <dennis@stosberg.net>
To: git@vger.kernel.org
Subject: Re: [PATCH] Update documentation for git-format-patch
Date: Wed, 31 May 2006 19:24:41 +0200 [thread overview]
Message-ID: <20060531172441.G2b322ff2@leonov.stosberg.net> (raw)
In-Reply-To: <e5kcfi$124$1@sea.gmane.org>
Jakub Narebski wrote:
> Dennis Stosberg wrote:
>
> > - Display suspicious lines in the patch. The definition
> > - of 'suspicious lines' is currently the lines that has
> > - trailing whitespaces, and the lines whose indentation
> > - has a SP character immediately followed by a TAB
> > - character.
>
> So is this option also lost in built-in git-format-patch?
Johannes Schindelin made that one a diff option, so it can be used in
other ways, too. I think it should be documented in diff-options.txt.
> > -CONFIGURATION
> > -You can specify extra mail header lines to be added to each
> > -message in the repository configuration as follows:
> > -
> > -[format]
> > - headers = "Organization: git-foo\n"
>
> So is this configuration option also lost in built-in git-format-patch?
Grep'ing the sources, I couldn't find any trace of it.
Regards,
Dennis
prev parent reply other threads:[~2006-05-31 17:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <93c3eada0605310332p19241861g466e1516a2aaf0df@mail.gmail.com>
2006-05-31 11:11 ` format-patch signoff argument no longer works Geoff Russell
2006-05-31 11:28 ` Matthias Kestenholz
2006-05-31 13:58 ` Seth Falcon
2006-05-31 14:09 ` Johannes Schindelin
2006-05-31 19:02 ` Junio C Hamano
2006-05-31 19:19 ` J. Bruce Fields
2006-05-31 19:43 ` Seth Falcon
2006-05-31 22:14 ` [PATCH] format-patch --signoff Junio C Hamano
2006-05-31 22:42 ` Johannes Schindelin
2006-05-31 23:16 ` Junio C Hamano
2006-05-31 23:31 ` Johannes Schindelin
2006-05-31 14:14 ` [PATCH] Update documentation for git-format-patch Dennis Stosberg
2006-05-31 15:00 ` Johannes Schindelin
2006-05-31 15:24 ` Jakub Narebski
2006-05-31 17:24 ` Dennis Stosberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060531172441.G2b322ff2@leonov.stosberg.net \
--to=dennis@stosberg.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).