From: Junio C Hamano <gitster@pobox•com>
To: Jeremy White <jwhite@codeweavers•com>
Cc: git@vger•kernel.org
Subject: Re: [PATCH v2] Enable setting attach as the default in .gitconfig for git-format-patch.
Date: Thu, 12 Feb 2009 13:01:25 -0800 [thread overview]
Message-ID: <7vljsbl68q.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 4994459B.8090002@codeweavers.com
Jeremy White <jwhite@codeweavers•com> writes:
> diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt
> index 11a7d77..f89f73c 100644
> --- a/Documentation/git-format-patch.txt
> +++ b/Documentation/git-format-patch.txt
> @@ -10,7 +10,8 @@ SYNOPSIS
> --------
> [verse]
> 'git format-patch' [-k] [-o <dir> | --stdout] [--thread]
> - [--attach[=<boundary>] | --inline[=<boundary>]]
> + [--attach[=<boundary>] | --inline[=<boundary>] |
> + [--noattach]]
Hmph, don't we usually do this with --no-attach? Especially when
format-patch starts using parse_options, I suspect that would be how the
API gives negated options natively.
If there are no other issues people find in this patch, I'll amend it to
use dash between no and attach and apply (hence no need to resend).
Thanks.
next prev parent reply other threads:[~2009-02-12 21:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 15:51 [PATCH v2] Enable setting attach as the default in .gitconfig for git-format-patch Jeremy White
2009-02-12 21:01 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-08 3:26 Jeremy White
2009-02-08 5:10 ` Boyd Stephen Smith Jr.
2009-02-08 16:01 ` Jeremy White
2009-02-08 17:28 ` Johannes Schindelin
2009-02-09 12:34 ` Michael J Gruber
2009-02-09 13:25 ` Ben Bucksch
2009-02-09 13:36 ` Johannes Schindelin
2009-02-09 13:50 ` Michael J Gruber
2009-02-09 14:39 ` Boyd Stephen Smith Jr.
2009-02-09 13:52 ` Ben Bucksch
2009-02-09 14:49 ` Johannes Schindelin
2009-02-10 1:41 ` Junio C Hamano
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=7vljsbl68q.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jwhite@codeweavers$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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