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

Re: Git roadmap (How read What's cooking in git.git)

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Nov 18, 2010, 14:41 UTC
Message-ID
<AANLkTi=ggFa4mwd=vkxJYq-JgCT=Tkmkv-0RQ_cqeYWm@mail.gmail.com>
In-Reply-To
<AANLkTikDyxUWBnCzxRNA9MzBmr0LrqDb1ggNjOTc=7DR@mail.gmail.com>
On Thu, Nov 18, 2010 at 8:55 AM, Sebastien Douche <sdouche@gmail.com> wrote:
>> You can get something like a roadmap just by following what people are
>> working on, and asking them what they want to do next.
>
> Understood. I will make it.
Any chance you can revive the "Git Chronicles" [1]?

Junio is too busy to update it (see his reply in [1]). I'm sure it would be really appreciated.

[1] http://mid.gmane.org/201007081057.51946.jnareb@gmail.com
-- 
Duy
Previous: Sebastien DoucheNext: Jakub Narebski
Message 4 of 7 in “Git roadmap (How read What's cooking in git.git)”
  1. Sebastien DoucheNov 16, 2010
  2. Ævar Arnfjörð BjarmasonNov 16, 2010
  3. Sebastien DoucheNov 18, 2010
  4. Nguyen Thai Ngoc DuyNov 18, 2010
  5. Jakub NarebskiNov 18, 2010
  6. Sebastien DoucheNov 18, 2010
  7. Sebastien DoucheNov 18, 2010

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.