Repository Reorganization Question

[Simon Marlow]

I don't feel terribly strongly about this, but I'd rather not clutter up 
the commit messages.  As long as we keep the old testsuite.git 
repository attached to Trac, we can always find the old commits, and 
Google is a good hash table for SHA-1 keys.

Cheers,
Simon

On 10/12/2013 21:42, Herbert Valerio Riedel wrote:
> Hi Ben,
>
> On 2013-12-10 at 17:53:23 +0100, Ben Gamari wrote:
>> If the old commit IDs are really needed, one would think it wouldn't be
>> too hard to write them into the commit message while rewriting
>> history. That way you could at least `git log --grep` IIRC.
>
> Good idea, that's quite easy actually, I just need to perform
>
>   git filter-branch \
>     --msg-filter 'cat - && echo && echo "(original commit: [$GIT_COMMIT/testsuite])"'
>
> as the first rewrite step (so that the $GIT_COMMIT variable still points
> to the original commit hash ids), and then the imported commits will
> look like e.g.
>
> ,----
> | commit afe483f9b9e0eadda178f9f6786d835ea7b8395c
> | Author: Joachim Breitner <mail at joachim-breitner.de>
> | Date:   Mon Dec 9 15:40:20 2013 +0000
> |
> |     Use -ddump-strsigs in tests/stranal/sigs
> |
> |     because it is more reliable than the previous GHC plugin (no need to
> |     support annotations etc.), plus it works nicely with "make accept".
> |
> |     (original commit: [323cab22d65ea88410a607ef22db23198c03e305/testsuite])
> `----
>
> So if we want it that way, it's easily accomplished...
>
> Cheers,
>    hvr
>