From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 01/12] git-grep: read config
Date: Fri, 25 Jul 2008 01:45:58 +0700 [thread overview]
Message-ID: <fcaeb9bf0807241145y16bb5f94q9f7e3c09c3184782@mail.gmail.com> (raw)
In-Reply-To: <20080724171519.GA21043@sigill.intra.peff.net>
On 7/25/08, Jeff King <peff@peff.net> wrote:
> On Wed, Jul 23, 2008 at 09:55:35PM +0700, Nguyen Thai Ngoc Duy wrote:
>
> >
> > Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
>
>
> The commit message is a bit lacking...what config are we interested in?
core.sparsecheckout, but I will probably stay away from config.
--
Duy
next prev parent reply other threads:[~2008-07-24 18:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 14:55 [PATCH 01/12] git-grep: read config Nguyễn Thái Ngọc Duy
2008-07-24 17:15 ` Jeff King
2008-07-24 18:45 ` Nguyen Thai Ngoc Duy [this message]
2008-07-24 18:53 ` Sverre Rabbelier
2008-07-24 19:03 ` Nguyen Thai Ngoc Duy
2008-07-24 19:12 ` Sverre Rabbelier
2008-07-24 19:16 ` Jay Soffian
2008-07-24 18:58 ` Jeff King
2008-07-24 19:07 ` Nguyen Thai Ngoc Duy
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=fcaeb9bf0807241145y16bb5f94q9f7e3c09c3184782@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.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).