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
Jakub Narebski <jnareb@gmail.com>
Date
Nov 18, 2010, 14:05 UTC
Message-ID
<m3ipzu682o.fsf@localhost.localdomain>
In-Reply-To
<AANLkTimtUz3L0F_iOpH7YuYpyoutPqtevPj-Tjo6MRcs@mail.gmail.com>
Sebastien Douche <sdouche@gmail.com> writes:
Show 8 quoted lines
> I'm starting a french blog[1] on git to support workshops[2]. The goal
> is to explain deeply the philosophy, the commands and subcommands,
> workflows, etc. And also to aggregate headlines of the git world,
> follow events and announce git releases. For the latter, it's a bit
> hard (for a non core developer) to follow the development. From your
> point of view, how we could set up a roadmap and a "what's new"?
> 
> [1] http://blog.gitfr.net
There is Junio's blog which sometimes contain interesting bits about git:
  http://gitster.livejournal.com/

There is also "A git blog looking to be official" (with announcements and git top links, etc)

  http://gitlog.wordpress.com/

I know that it doesn't really answer your question, but Git User's Surveys included question about what features one would want in Git, see for example

  https://git.wiki.kernel.org/index.php/GitSurvey2010
-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: Nguyen Thai Ngoc DuyNext: Sebastien Douche
Message 5 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.