From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Thomas Rast <trast@inf.ethz.ch>
Cc: <git@vger.kernel.org>
Subject: Re: [PATCH] bash-completion: add --edit-description to choices for branch
Date: Mon, 6 Feb 2012 19:16:08 -0500 [thread overview]
Message-ID: <4F306D48.1060103@windriver.com> (raw)
In-Reply-To: <871uq7sfwb.fsf@thomas.inf.ethz.ch>
On 12-02-06 06:25 PM, Thomas Rast wrote:
> Paul Gortmaker <paul.gortmaker@windriver.com> writes:
>
>> Support was recently added to allow storing a branch description,
>> so teach bash completion about it.
>
> See 48c07d8 (completion: --edit-description option for git-branch,
> 2012-01-29) which is already in next.
OK thanks, I did a quick google, didn't get any obvious
clues that it was done already, but must have missed it.
P.
>
prev parent reply other threads:[~2012-02-07 0:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 17:03 [PATCH] bash-completion: add --edit-description to choices for branch Paul Gortmaker
2012-02-06 23:25 ` Thomas Rast
2012-02-07 0:16 ` Paul Gortmaker [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=4F306D48.1060103@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=git@vger.kernel.org \
--cc=trast@inf.ethz.ch \
/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).