Re: What's cooking in git/spearce.git (topics)

From: Theodore Tso <tytso@mit.edu>
Date: Oct 23, 2007, 01:21 UTC
Message-ID: <20071023012140.GC22997@thunk.org>
In-Reply-To: <7v3aw2aaxu.fsf@gitster.siamese.dyndns.org>

On Mon, Oct 22, 2007 at 06:15:09PM -0700, Junio C Hamano wrote:

Show 11 quoted lines

> >
> > I've recently started trying to use some of the scripts in "todo" to
> > send similar "What's cooking" messages, and started wondering if they
> > were what Junio actually used in production to send his notes.  For
> > example, the scripts don't work particularly well if the refs have
> > been packed.  So I had to make changes such as these so they would
> > work for me.
> 
> Sorry, WI is for "what's in", WC is for "what's cooking".  I
> should remove PU and RB from there.
>

I assume PU is what you used to build your proposed-update branch? I'm actually trying to use it, and it is useful, although it hasn't been working for me completely perfectly. I've still been trying to figure out if the reason why it hasn't been working quite right is due to my not understanding how to use it correctly, or whether you don't use it these days.

One question which I have had about the WC script is that if I manually add a commit to the next branch, it ends up showing up in all of the topic branches as a commit that was part of that topic branch which is in next. So I can manually edit the output of WC to remove the spurious commit, or I could make it be a rule that all new commits either must go against the master branch, or be put in a topic branch based off of master, and then merged into next. Or maybe I'm not understanding how to make the WC and git-topic.perl script work and sing for me perfectly?

					- Ted