From: "SZEDER Gábor" <szeder@ira•uka.de>
To: "Shawn O. Pearce" <spearce@spearce•org>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] bash: __git_find_subcommand function
Date: Mon, 10 Mar 2008 15:51:01 +0100 [thread overview]
Message-ID: <20080310145101.GA6468@neumann> (raw)
In-Reply-To: <20080308022342.GY8410@spearce.org>
On Fri, Mar 07, 2008 at 09:23:42PM -0500, Shawn O. Pearce wrote:
> Yup, you understood it correctly. You found a cluster of "copy and
> paste programming" and I am happy to see it cleaned up. Thanks.
Thanks. I will send out the updated patches soon.
Gábor
prev parent reply other threads:[~2008-03-10 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 14:58 [PATCH] bash: __git_find_subcommand function SZEDER Gábor
2008-03-08 2:23 ` Shawn O. Pearce
2008-03-10 14:51 ` SZEDER Gábor [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=20080310145101.GA6468@neumann \
--to=szeder@ira$(echo .)uka.de \
--cc=git@vger$(echo .)kernel.org \
--cc=spearce@spearce$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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