Re: [PATCH 2/2] filter-branch: update current branch when rewritten

From: Shawn O. Pearce <spearce@spearce.org>
Date: Oct 19, 2007, 00:06 UTC
Message-ID: <20071019000604.GM14735@spearce.org>
In-Reply-To: <18199.21729.535096.397497@lisa.zopyra.com>

Bill Lear <rael@zopyra.com> wrote:

Show 13 quoted lines

> On Wednesday, October 17, 2007 at 03:23:10 (+0100) Johannes Schindelin writes:
> >
> >Earlier, "git filter-branch --<options> HEAD" would not update the
> >working tree after rewriting the branch.  This commit fixes it.
> >
> >Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> >---
> >
> >	Bill, I hope this clarifies some things for you, too...
> 
> Thanks very much.  I hope so, too.  I'll pull this in to my tree
> when it gets into the git repository (how do I know when that happens,
> or do I just need to pull and inspect?).

This is actually already in my maint branch:

  git://repo.or.cz/git/spearce.git
  http://repo.or.cz/r/git/spearce.git

The best way to know if a given patch has been applied is to just fetch every so often and look. But you are also subscribed to the mailing list and there's usually a weekly "What's in git.git" and a "What's cooking in git.git" messages sent describing the recent changes. Monitoring these can also tell you when it may be a good time for you to pull in a more recent version.

My last What's in/What's cooking messages were sent out on Monday. I've got a lot of stuff from folks since then going into my tree (the above is one of them) so I'll probably wrap up this week with another set of messages tomorrow.

Of course the maintainer could send an email for every patch that he/she applies, but the mailing list volume is already quite high. Junio (and myself) both prefer to not bother responding to accepted patches when they come from regular contributors, as we know the regular contributor will be pulling in the near future anyway.

-- 
Shawn.