From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Thomas Rast <trast@student.ethz.ch>
Cc: git@vger.kernel.org, gitster@pobox.com,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH] bash completion: Add long options for 'git describe'
Date: Fri, 25 Jul 2008 15:15:32 +0200 [thread overview]
Message-ID: <20080725131532.GB6701@neumann> (raw)
In-Reply-To: <1216980170-14136-1-git-send-email-trast@student.ethz.ch>
Hi,
On Fri, Jul 25, 2008 at 12:02:50PM +0200, Thomas Rast wrote:
> ---
Signed off by?
> _git_describe ()
> {
> + __git_has_doubledash && return
This line is superfluous, because 'git describe' does not have any path
arguments.
Gábor
next prev parent reply other threads:[~2008-07-25 13:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 10:02 [PATCH] bash completion: Add long options for 'git describe' Thomas Rast
2008-07-25 13:15 ` SZEDER Gábor [this message]
2008-07-25 16:20 ` Shawn O. Pearce
2008-07-26 10:25 ` Thomas Rast
2008-07-26 10:26 ` Thomas Rast
2008-07-26 21:52 ` Shawn O. Pearce
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=20080725131532.GB6701@neumann \
--to=szeder@ira.uka.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.org \
--cc=trast@student.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).