From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Sun, 14 Sep 2008 16:29:59 GMT
Subject: Re: [TOY PATCH] filter-branch: add option --delete-unchanged
Message-ID: <94a0d4530809140929s1728a7aevb9f4b0a0469eba0c@mail.gmail.com>
In-Reply-To: <1218226224-25273-1-git-send-email-trast@student.ethz.ch>

On Fri, Aug 8, 2008 at 11:10 PM, Thomas Rast <trast@student.ethz.ch> wrote:
> With --delete-unchanged, we nuke refs whose targets did not change
> during rewriting.  It is intended to be used along with
> --subdirectory-filter to clean out old refs from before the first
> commit to the filtered subdirectory.  (They would otherwise keep the
> old history alive.)
>
> Obviously this is a rather dangerous mode of operation.
>
> Note the "sort -u" is required: Without it, --all includes
> 'origin/master' twice (from 'origin/master' and via 'origin/HEAD'),
> and the second pass concludes it is unchanged and nukes the ref.

This is really useful, why isn't it merged?

Personally I use filter-branch to, duh, filter a branch, so I don't
want the commit objects that are not filtered, nor the refs to them.

-- 
Felipe Contreras