From: Junio C Hamano <gitster@pobox.com>
To: Brandon Casey <casey@nrlssc.navy.mil>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 1/2] filter-branch: only print usage information when no arguments supplied
Date: Wed, 30 Jan 2008 17:34:55 -0800 [thread overview]
Message-ID: <7v3asehj5s.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <47A112C5.8010903@nrlssc.navy.mil> (Brandon Casey's message of "Wed, 30 Jan 2008 18:13:57 -0600")
Brandon Casey <casey@nrlssc.navy.mil> writes:
> Testing for whether command line arguments were supplied was being
> performed during option parsing. This had the side effect of
> printing usage information when a more appropriate error message
> would have been printed had the script been allowed to continue.
>
> Now this:
>
> git filter-branch
>
> will print usage information.
>
> And these:
>
> git filter-branch -d /tmp/work-dir
> git filter-branch <non-existant-revision>
> git filter-branch --
> git filter-branch -- <non-existant-revision>
>
> will print a message informing the user that filter-branch did
> not know which reference to rewrite. Without this patch the
> one with '-d' would also print usage information.
>
> Signed-off-by: Brandon Casey <casey@nrlssc.navy.mil>
> ---
>
>
> I prefer my original patch since I think it is consistent
> with the git interface.
I'd refrain from commenting on if it is consistent or not with
"the git interface".
But I would say I prefer your original better than this one.
Will apply.
next prev parent reply other threads:[~2008-01-31 1:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 19:33 [PATCH] filter-branch: assume HEAD if no revision supplied Brandon Casey
2008-01-30 20:35 ` Johannes Schindelin
2008-01-30 21:03 ` Junio C Hamano
2008-01-30 23:35 ` Brandon Casey
2008-01-31 0:13 ` [PATCH 1/2] filter-branch: only print usage information when no arguments supplied Brandon Casey
2008-01-31 1:34 ` Junio C Hamano [this message]
2008-01-31 2:05 ` Brandon Casey
2008-01-31 2:44 ` Junio C Hamano
[not found] ` <1201738186-28132-1-git-send-email-casey@nrlssc.navy.mil>
2008-01-31 0:15 ` [PATCH 2/2] git-filter-branch.sh: don't use --default when calling rev-list Brandon Casey
2008-01-31 0:49 ` Johannes Schindelin
2008-01-31 1:35 ` Brandon Casey
2008-01-31 9:17 ` Andreas Ericsson
2008-01-31 9:27 ` Junio C Hamano
2008-01-31 11:07 ` Johannes Schindelin
2008-01-31 0:16 ` [PATCH] filter-branch: assume HEAD if no revision supplied Johannes Schindelin
2008-01-31 0:20 ` Brandon Casey
2008-01-31 0:41 ` [PATCH] filter-branch docs: remove brackets so not to imply revision arg is optional Brandon Casey
2008-01-31 1:22 ` Junio C Hamano
2008-01-31 1:53 ` Johannes Schindelin
2008-01-31 16:29 ` Brandon Casey
2008-01-31 21:53 ` 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=7v3asehj5s.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=casey@nrlssc.navy.mil \
--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).