Re: Draft release notes for v1.5.3, as of -rc1

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jul 14, 2007, 14:22 UTC
Message-ID: <Pine.LNX.4.64.0707141517450.14781@racer.site>
In-Reply-To: <20070713092908.GO1528MdfPADPa@greensroom.kotnet.org>

Hi,

On Fri, 13 Jul 2007, Sven Verdoolaege wrote:

Show 8 quoted lines

> On Thu, Jul 12, 2007 at 11:40:39PM -0700, Junio C Hamano wrote:
> >   - "git-filter-branch" lets you rewrite the revision history of
> >     the current branch, creating a new branch. You can specify a
> >     number of filters to modify the commits, files and trees.
> 
> Are you sure you want to announce this so publicly given that
> Dscho has basically declared git-filter-branch dead?
> (I know, I'm mostly to blame.)

It is really unfortunate that rewrite-commits came in so late in the release cycle, and I am quite sure it should not be in 1.5.3. There is just too much new in it, and too many things to flesh out.

Junio, if you want to include it in 1.5.3, it should be marked as alpha code, as it has not seen any time in "next", let alone "master".

However, no matter if rewrite-commits is included in 1.5.3, I am not sure what to do about filter-branch.

Since it saw a lot of testing in its admin-rewritehist form, and has had at least some eye pairs looking over it, I have the feeling that it is stable enough to include. How to tell people that it will soon be obsoleted by rewrite-commits, I have no idea.

It would be a much less difficult problem if the syntax of filter-branch and rewrite-commits was identical. Maybe we should make it so, by changing filter-branch?

Thoughts?

Ciao, Dscho