All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Sebastien Douche <sdouche@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: Git roadmap (How read What's cooking in git.git)
Date: Thu, 18 Nov 2010 06:05:51 -0800 (PST)	[thread overview]
Message-ID: <m3ipzu682o.fsf@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimtUz3L0F_iOpH7YuYpyoutPqtevPj-Tjo6MRcs@mail.gmail.com>

Sebastien Douche <sdouche@gmail.com> writes:

> 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

  parent reply	other threads:[~2010-11-18 14:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16 12:53 Git roadmap (How read What's cooking in git.git) Sebastien Douche
2010-11-16 13:38 ` Ævar Arnfjörð Bjarmason
2010-11-18  1:55   ` Sebastien Douche
2010-11-18 14:41     ` Nguyen Thai Ngoc Duy
     [not found]       ` <m3eiai657o.fsf@localhost.localdomain>
2010-11-18 15:31         ` Sebastien Douche
2010-11-18 14:05 ` Jakub Narebski [this message]
2010-11-18 15:25   ` Sebastien Douche

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=m3ipzu682o.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sdouche@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.