From: Jakub Narebski <jnareb@gmail.com>
Date: Wed, 03 Jul 2013 23:46:19 GMT
Subject: Re: Feature request:
Message-ID: <loom.20130704T013747-723@post.gmane.org>
In-Reply-To: <7vppuzfrde.fsf@alter.siamese.dyndns.org>

[I'm sorry about breaking Cc: chain - responding via GMane web interface]

Junio C Hamano <gitster <at> pobox.com> writes:
> Ed Hutchins <eh <at> demeterr.com> writes:
> 
> > I'm not trying to change the way git does things (which works perfectly
> > well), I'm asking for some extra information to be added to the commit
> > so that analysis of the ancestry graph can be tied to the branch topics
> > that the original author was working from. [...]
[...]
> It is not just misleading but is actively wrong to recording the
> name of the original branch in commits and carrying them forward via
> rebase. If you want a record of what a group of commits were about,
> the right time to do so is when you merge.
[...]

There is even git-resurrect.sh script in 'contrib/' that makes
use of that practice to find merged-in and deleted branches,
and resurrect them (among other tools).

-- 
Jakub Narębski