git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 01/12] git-grep: read config

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Jul 24, 2008, 19:07 UTC
Message-ID
<fcaeb9bf0807241207y460ebe52o9e9f4958ab07679b@mail.gmail.com>
In-Reply-To
<20080724185844.GC21186@sigill.intra.peff.net>
On 7/25/08, Jeff King <peff@peff.net> wrote:
Show 9 quoted lines
> On Fri, Jul 25, 2008 at 01:45:58AM +0700, Nguyen Thai Ngoc Duy wrote:
>
>  > > The commit message is a bit lacking...what config are we interested in?
>  >
>  > core.sparsecheckout, but I will probably stay away from config.
>
>
> Right, I kind of guessed that from reading the rest of the series. But
>  that sort of "why" really should go into the commit message.

There was "why" in the commit before but I wanted to make the first two patches independent to this series. Turns out bad, I think :)

-- 
Duy
Previous: Jeff King
Message 9 of 9 in “git-grep: read config”
  1. 01/12 git-grep: read configNguyễn Thái Ngọc Duy, Jul 23, 2008
  2. Jeff KingJul 24, 2008
  3. Nguyen Thai Ngoc DuyJul 24, 2008
  4. Sverre RabbelierJul 24, 2008
  5. Nguyen Thai Ngoc DuyJul 24, 2008
  6. Sverre RabbelierJul 24, 2008
  7. Jay SoffianJul 24, 2008
  8. Jeff KingJul 24, 2008
  9. Nguyen Thai Ngoc DuyJul 24, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.