From: Jonathan Nieder <jrnieder@gmail.com>
To: Neal Kreitzinger <neal@rsss.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: Tonight's pushout
Date: Thu, 9 Dec 2010 14:01:43 -0600 [thread overview]
Message-ID: <20101209200143.GC6884@burratino> (raw)
In-Reply-To: <idotn7$9o7$1@dough.gmane.org>
Neal Kreitzinger wrote:
> "prerelease freeze" is not in the git-workflows manpage. I'm interested in
> how you-all do this because I use the git-workflows mangpage to help me
> figure out my workflows. Can someone explain?
See http://en.wikipedia.org/wiki/Freeze_(software_engineering)
In git's incarnation of it, presumably the idea is that new features
do not get merged to 'master' (while they still would be merged to
'pu' and perhaps 'next').
See also <http://sites.google.com/site/maintnotes/> for some direct
discussion of the branches used by git.git.
Hope that helps,
Jonathan [1]
[1] Unrelated note: please try to preserve the cc list in replies
(i.e., "reply-to-all-by-mail" rather than "followup").
next prev parent reply other threads:[~2010-12-09 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 2:24 Tonight's pushout Junio C Hamano
2010-12-08 21:35 ` Neal Kreitzinger
2010-12-09 20:01 ` Jonathan Nieder [this message]
2010-12-10 1:25 ` Neal Kreitzinger
-- strict thread matches above, loose matches on Subject: below --
2010-08-10 5:35 Junio C Hamano
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=20101209200143.GC6884@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=neal@rsss.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).