From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Raman Gupta <rocketraman@fastmail.fm>, git@vger.kernel.org
Subject: Re: Reference for git.git release process
Date: Wed, 25 Mar 2009 20:34:44 -0700 [thread overview]
Message-ID: <7v3ad1ufcb.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090326022757.GC5835@coredump.intra.peff.net> (Jeff King's message of "Wed, 25 Mar 2009 22:27:58 -0400")
Jeff King <peff@peff.net> writes:
> On Wed, Mar 25, 2009 at 12:30:31PM -0700, Junio C Hamano wrote:
>
>> I do not answer "generally" part, but in git.git, I do not publish heads
>> of individual topic branches. I could, but simply I don't, because that
>> has been the way I've operated so far, and I am too lazy to change my
>> configuration.
>
> I don't think it is a big problem in practice.
Both times Shawn took over the maintainership from me in October for the
past few years (and I will ask him to this year, too, although I do not
know if he is willing to take it again yet), it would have made his life
(and possibly everybody who had his topic in flight) much easier if they
were public. Last year I sent him for-each-ref output offline before I
took off to make it a bit easier on him (my disappearance two years ago
was unscheduled and I couldn't do that).
next prev parent reply other threads:[~2009-03-26 3:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 18:32 Reference for git.git release process Raman Gupta
2009-03-25 19:30 ` Junio C Hamano
2009-03-25 22:03 ` Raman Gupta
2009-03-25 23:41 ` Junio C Hamano
2009-03-26 3:26 ` Junio C Hamano
2009-03-26 2:27 ` Jeff King
2009-03-26 3:13 ` Junio C Hamano
2009-03-26 3:15 ` Jeff King
2009-03-26 3:28 ` Junio C Hamano
2009-03-26 3:49 ` Jeff King
2009-03-26 3:34 ` Junio C Hamano [this message]
2009-03-26 17:03 ` Shawn O. Pearce
2009-03-26 8:05 ` Andreas Ericsson
2009-03-26 14:29 ` Raman Gupta
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=7v3ad1ufcb.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=rocketraman@fastmail.fm \
/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).