From: Andreas Ericsson <ae@op5.se>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Sixt <j.sixt@viscovery.net>, git@vger.kernel.org
Subject: Re: [PATCH] git-branch --with=commit
Date: Thu, 08 Nov 2007 10:17:52 +0100 [thread overview]
Message-ID: <4732D440.2020504@op5.se> (raw)
In-Reply-To: <7vejf140jd.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote:
> Johannes Sixt <j.sixt@viscovery.net> writes:
>
>> Junio C Hamano schrieb:
>
>>> With this patch, I could do this to find out which topic
>>> branches already contain the faulty commit:
>>>
>>> $ git branch --with=maint^ | grep /
>>> xx/maint-fix-foo
>> It'd be helpful if you could construct the example in this commit
>> message such that you don't need the "grep /" here; otherwise, the
>> reader doesn't know which part of the effect is hidden by the grep.
>
> Yeah, in the example sequence, I think only maint itself and
> xx/maint-fix-foo are shown, so there is no need for grep.
And "maint" could certainly be stripped by the code itself, since the
user can reasonably be expected to know that plain maint will have
everything maint^ has.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-11-08 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 23:15 [PATCH] git-branch --with=commit Junio C Hamano
2007-11-07 23:33 ` Jakub Narebski
2007-11-08 0:09 ` Johannes Schindelin
2007-11-08 2:05 ` Junio C Hamano
2007-11-08 3:02 ` Johannes Schindelin
2007-11-08 7:36 ` Johannes Sixt
2007-11-08 8:13 ` Junio C Hamano
2007-11-08 9:17 ` Andreas Ericsson [this message]
2007-11-15 17:27 ` Jan Hudec
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=4732D440.2020504@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
/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).