Repository Reorganization Question

Carter Schonwald carter.schonwald at
Fri Dec 6 17:47:47 UTC 2013

personally i don't care about the bandwidth, and others are correct about
the value of logs. If theres a way to get both, awesome!  If not, 20mb here
and there i don't care.

On Fri, Dec 6, 2013 at 11:26 AM, Johan Tibell <johan.tibell at>wrote:

> On Fri, Dec 6, 2013 at 4:43 PM, Herbert Valerio Riedel <hvr at>wrote:
>> On 2013-12-06 at 13:50:55 +0100, Johan Tibell wrote:
>> > Whichever way to go, we should write down the options and consequences
>> and
>> > communicating them widely enough so no core devs get surprised.
>> >
>> > Commit IDs for the test suite are referenced in e.g. various Trac
>> issues,
>> > on mailing lists (although rarely), and perhaps even in code.
>> I hinted at in an earlier post, the old commit-ids will still
>> allow to find the original commit; for isntance, there's already the
>> find-commit-by-sha1 service at
>> which searches all repos hosted at for the given sha1
>> prefix; there's also a convenient text-entry field at
>> which allows you to copy'n'paste any commit-ids
>> you might come across in emails, irc logs, trac comments or even commit
>> messages...
>> ...does this lookup-service alleviate your concerns?
> Personally I think it's still much friction; another thing to remember. Is
> it really worth it for a couple of megs of bandwidth* and some disk space?
> If it really is I believe git has some facility for nuking the data of old
> commits. That facility exists for the case when someone committed something
> sensitive to the code base that should never have been there.
> * GitHub's bandwidth if you use that mirror.
> -- Johan
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the ghc-devs mailing list