From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Raman Gupta <rocketraman@fastmail.fm>, git@vger.kernel.org
Subject: Re: Reference for git.git release process
Date: Wed, 25 Mar 2009 22:27:58 -0400 [thread overview]
Message-ID: <20090326022757.GC5835@coredump.intra.peff.net> (raw)
In-Reply-To: <7viqlxz9go.fsf@gitster.siamese.dyndns.org>
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. But every once in a while
I have had to dig through pu to re-create a topic branch manually. And I
believe Thomas Rast posted a script to do so automatically. So I think
there is some indication that people might find this information useful,
but I don't feel too strongly about it.
> Also I suspect it would make my life more cumbersome
> because I have to prune stale topics from the public repositories from
> time to time.
Mirror mode would handle this automatically, but it unfortunately also
ignores your push refspec. So any cruft or work-in-progress refs in your
repository would be pushed.
-Peff
next prev parent reply other threads:[~2009-03-26 2:29 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 [this message]
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
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=20090326022757.GC5835@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).