From: | Christopher Browne <cbbrowne(at)gmail(dot)com> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Old git repo |
Date: | 2010-08-19 21:33:44 |
Message-ID: | AANLkTimNZepkfmaK3_+-G+KG4uioAV7FJeD52BfQYRU6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Aug 19, 2010 at 5:29 PM, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> The new git repository will have different SHA1s for all of the commits,
> so any old SHA1s will be useless without the old repository.
>
> Hopefully nobody used links to specific commits (or SHA1s) pointing to
> the old git repository for anything important. But I found myself doing
> so occasionally for unimportant things (if it was important, I included
> the date as a safeguard) -- so I assume a few other people did, as well.
>
> Would it be worth keeping the old git repository around in a read-only
> mode, just in case people have links/SHA1s floating around for it?
Perhaps "http://git.postgresql.org/gitweb?p=postgresql-before-official-git-migration.git;a=summary"
--
http://linuxfinances.info/info/linuxdistributions.html
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-08-19 21:35:01 | Re: COPY FROM/TO losing a single byte of a multibyte UTF-8 sequence |
Previous Message | Magnus Hagander | 2010-08-19 21:30:40 | Re: Old git repo |