From: Sebastien Douche <sdouche@gmail.com>
To: Jakub Narebski <jnareb@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 16:25:02 +0100 [thread overview]
Message-ID: <AANLkTi=BhjEfTtsKd-gTch8M7Af7cuTkrnLORNAz9gwX@mail.gmail.com> (raw)
In-Reply-To: <m3ipzu682o.fsf@localhost.localdomain>
On Thu, Nov 18, 2010 at 15:05, Jakub Narebski <jnareb@gmail.com> wrote:
> http://gitster.livejournal.com/
> http://gitlog.wordpress.com/
> https://git.wiki.kernel.org/index.php/GitSurvey2010
thank you Jakub for the links but I know all ;)
--
Sebastien Douche <sdouche@gmail.com>
Twitter: @sdouche (agile, lean, python, git, open source)
prev parent reply other threads:[~2010-11-18 15:25 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
2010-11-18 15:25 ` Sebastien Douche [this message]
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='AANLkTi=BhjEfTtsKd-gTch8M7Af7cuTkrnLORNAz9gwX@mail.gmail.com' \
--to=sdouche@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@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 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).