From: "Shawn O. Pearce" <spearce@spearce.org>
To: "SZEDER Gábor" <szeder@ira.uka.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] bash: remove unnecessary conditions when checking for subcommands
Date: Mon, 10 Mar 2008 19:54:32 -0400 [thread overview]
Message-ID: <20080310235432.GJ8410@spearce.org> (raw)
In-Reply-To: <1205161345-21120-1-git-send-email-szeder@ira.uka.de>
SZEDER Gbor <szeder@ira.uka.de> wrote:
> Checking emptyness of $command is sufficient.
>
> Signed-off-by: SZEDER Gábor <szeder@ira.uka.de>
Thanks. I have your entire series in a branch that I will
be asking Junio to merge.
--
Shawn.
prev parent reply other threads:[~2008-03-10 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 15:02 [PATCH 1/2] bash: remove unnecessary conditions when checking for subcommands SZEDER Gábor
2008-03-10 15:02 ` [PATCH 2/2] bash: refactor searching for subcommands on the command line SZEDER Gábor
2008-03-10 15:02 ` [PATCH] bash: add new 'git stash' subcommands SZEDER Gábor
2008-03-10 15:02 ` [PATCH] bash: add 'git svn' subcommands and options SZEDER Gábor
2008-03-10 23:54 ` Shawn O. Pearce [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=20080310235432.GJ8410@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=szeder@ira.uka.de \
/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).