Loss of all package history following the recipe rename.

["John Willis" <John.Willis@Distant-earth.com>]

People,

Am I right in assuming that the decision to drop history for all packages
was really an unintentional side effect of this change? 

Unless I am going totally nuts the ONLY history for a given package now is
the 'git mv' commit.

i.e. on GIT HEAD

git log recipes/abiword/abiword-plugins_2.5.2.bb
commit 709c4d66e0b107ca606941b988bad717c0b45d9b
Author: Denys Dmytriyenko <denis@denix.org>
<snip, only the only commit logged>

On an old tree I keep for reference.

git log packages/abiword/abiword-plugins_2.5.2.bb
<snip, page after page of commits logged>

I just checked and the behavior of 'git mv' and it seems it's really just
'git rm && git add' under the hood, a few local experiments seem to confirm
that is the by design behavior (seems totally insane for a source control
system to do that however :-o) and after the 'git rm' the history is toast
as your then creating a new object with the same content as the removed one
:(.

I am not sure what we can do about this without resorting to a revert but it
looks like we may wish to look into something like 'git-filter-branch' (and
several other tools) to redo the move with something like the history
intact. 

That said, 'git-filter-branch' is a little scary and is proving to be more
then I really planned to be messing with on a sunny afternoon and I am not
totally sure if it will even do what is needed.

Does anyone have any other ideas or comment? Or have I completely lost the
plot and there is not really any problem other then in my local trees?

Regards,

John

--

> What is a grue?

The grue is a sinister, lurking presence in the dark places of the earth.
Its favourite diet is adventurers, but its insatiable appetite is tempered
by its fear of light. No grue has ever been seen by the light of day, and
few have survived its fearsome jaws to tell the tale.