From: "Philip Oakley" <philipoakley@iee.org>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2011, #03; Thu, 11) : Guidance for new contributors?
Date: Sat, 13 Aug 2011 19:40:08 +0100 [thread overview]
Message-ID: <AFD36BA266B14DAAA919E1AC1BDF0857@PhilipOakley> (raw)
In-Reply-To: 7vr54rpogf.fsf@alter.siamese.dyndns.org
From: "Junio C Hamano" <gitster@pobox.com>
Subject: What's cooking in git.git (Aug 2011, #03; Thu, 11)
> Here are the topics that have been cooking. Commits prefixed with '-' are
> only in 'pu' while commits prefixed with '+' are in 'next'.
>
> I am envisioning that we would declare feature freeze after most of the
> topics that are in 'next' as of today graduate to 'master' for the next
> release, and keep the remainder cooking for the cycle after that.
> Hopefully
> that would happen around 24th.
>
Would it it be possible to include a regular link to an explanation for new
contributors? It would guide and encourage any new readers of the list.
Would this one be suitable?
+ Guidance for contributions at
https://git.wiki.kernel.org/index.php/GitCommunity#Submitting
> --------------------------------------------------
> [New Topics]
> ....
Philip Oakley
Scotland UK.
next prev parent reply other threads:[~2011-08-13 18:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 22:34 What's cooking in git.git (Aug 2011, #03; Thu, 11) Junio C Hamano
2011-08-13 18:40 ` Philip Oakley [this message]
2011-08-16 16:40 ` What's cooking in git.git (Aug 2011, #03; Thu, 11) : Guidance for new contributors? Junio C Hamano
2011-08-14 8:44 ` What's cooking in git.git (Aug 2011, #03; Thu, 11) Ramkumar Ramachandra
2011-08-16 16:45 ` Junio C Hamano
2011-08-18 17:30 ` Ramkumar Ramachandra
2011-08-18 21:02 ` Pascal Obry
2011-08-18 22:34 ` Junio C Hamano
2011-08-20 21:11 ` Ramsay Jones
2011-08-23 18:09 ` Junio C Hamano
2011-08-24 10:14 ` Johannes Sixt
2011-08-21 9:02 ` Pascal Obry
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=AFD36BA266B14DAAA919E1AC1BDF0857@PhilipOakley \
--to=philipoakley@iee.org \
--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