On Fri, Aug 8, 2008 at 11:10 PM, Thomas Rast <trast@xxxxxxxxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
