From: Sebastien Douche <sdouche@gmail.com>
To: git list <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Git roadmap (How read What's cooking in git.git)
Date: Tue, 16 Nov 2010 13:53:01 +0100 [thread overview]
Message-ID: <AANLkTimtUz3L0F_iOpH7YuYpyoutPqtevPj-Tjo6MRcs@mail.gmail.com> (raw)
Hi Junio,
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
[2] 100% free, with 50 attendees for the first workshop, 70 for the second!
--
Sebastien Douche <sdouche@gmail.com>
Twitter: @sdouche (agile, lean, python, git, open source)
next reply other threads:[~2010-11-16 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 12:53 Sebastien Douche [this message]
2010-11-16 13:38 ` Git roadmap (How read What's cooking in git.git) Æ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
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=AANLkTimtUz3L0F_iOpH7YuYpyoutPqtevPj-Tjo6MRcs@mail.gmail.com \
--to=sdouche@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).