Repository Reorganization Question

Joachim Breitner mail at joachim-breitner.de
Mon Dec 9 09:15:25 UTC 2013


Hi,

Am Montag, den 09.12.2013, 10:04 +0100 schrieb Herbert Valerio Riedel:
> > But in contrast to the mailing list link issue, even if we rewrite the
> > testsuite before merging, it will be possible, although a bit more
> > tedious, to look up the corresponding new hash.
> 
> What I don't understand yet is, why do we need to know the new hash ids
> at all? If we come across an old hash-id, aren't we just interested in
> finding the commitdiff (and possibly neighbor commits) it refers to?

good point, I did not think of that. So if trac links are preserved
anyways, doesn’t that then solve the problem?

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
  mail at joachim-breitner.dehttp://www.joachim-breitner.de/
  Jabber: nomeata at joachim-breitner.de  • GPG-Key: 0x4743206C
  Debian Developer: nomeata at debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://www.haskell.org/pipermail/ghc-devs/attachments/20131209/6a70d690/attachment.sig>


More information about the ghc-devs mailing list