git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] format-patch: fix dashdash usage
Date: Fri, 27 Nov 2009 01:23:01 +0200	[thread overview]
Message-ID: <94a0d4530911261523q25147f12h2e6c9e4fe4f6b12b@mail.gmail.com> (raw)
In-Reply-To: <7v7htc3mqo.fsf@alter.siamese.dyndns.org>

On Fri, Nov 27, 2009 at 1:11 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Is it clearer what I meant?  More importantly, did I get the details
> right?

Yeah, I guess so.

> Hmm, I have not seen a clear "yes, because..." yet.

I'll repeat:
Not everyone has clean branches only with pertinent patches.

That's why revision filtering options make sense.

> For one thing, Documentation/git-format-patch.txt does not even hint that
> you can give pathspecs.  builtin_format_patch_usage[] doesn't, either.  As
> I wrote the initial version of format-patch I can say with some authority
> that use with pathspecs were never meant to be supported---if it works, it
> works by accident, giving long enough rope to users to potentially cause
> themselves harm.
>
> I am inclined to think that we shouldn't encourage use of pathspecs (just
> like we never encouraged use of options like --name-only that never makes
> sense in the context of the command) but I am undecided if we also should
> forbid the use of pathspecs (just like we did for --name-only recently).

How about 'git format-patch --full-diff'? Isn't that a valid way to
filter patches just like --author, --grep, and so on?

-- 
Felipe Contreras

  reply	other threads:[~2009-11-26 23:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-26 19:11 [PATCH 0/2] format-patch: fix dashdash Felipe Contreras
2009-11-26 19:11 ` [PATCH 1/2] format-patch: fix dashdash usage Felipe Contreras
2009-11-26 19:57   ` Junio C Hamano
2009-11-26 22:14     ` Felipe Contreras
2009-11-26 23:11       ` Junio C Hamano
2009-11-26 23:23         ` Felipe Contreras [this message]
2009-11-27  0:03           ` Junio C Hamano
2009-11-28 11:18             ` Felipe Contreras
2009-11-26 23:29         ` Junio C Hamano
2009-11-26 23:37         ` Björn Steinbrink
2009-11-26 19:12 ` [PATCH 2/2] format-patch: add test for dashdash Felipe Contreras

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=94a0d4530911261523q25147f12h2e6c9e4fe4f6b12b@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).