This is the mail archive of the
mailing list for the GCC project.
Re: Git conversion: disposition of old branches and tags
- From: <Paul_Koning at Dell dot com>
- To: <richard dot guenther at gmail dot com>
- Cc: <fw at deneb dot enyo dot de>, <jason at redhat dot com>, <gcc at gnu dot org>
- Date: Wed, 16 Sep 2015 15:49:48 +0000
- Subject: Re: Git conversion: disposition of old branches and tags
- Authentication-results: sourceware.org; auth=none
- References: <55F84AC9 dot 20501 at redhat dot com> <87oah3zk1i dot fsf at mid dot deneb dot enyo dot de> <CAFiYyc08jYUsDiB=em2fHc7_asd8ersZrDLT-hQzwN2wYRRQaQ at mail dot gmail dot com>
> On Sep 16, 2015, at 4:38 AM, Richard Biener <email@example.com> wrote:
> On Tue, Sep 15, 2015 at 7:09 PM, Florian Weimer <firstname.lastname@example.org> wrote:
>> Unlike Subversion branch deletion, Git branch deletion is permanent,
>> so this might not be the best option.
> We could have a 2nd git repository just containing deleted branches...
Agreed. A correctly designed source control system doesn't lose stuff, and the fact that GIT fails that test in the case of branches is rather disturbing. If the conversion would follow the GIT pattern, then the data it is going to delete should be preserved elsewhere. (I suppose another answer might be to keep the existing SVN server available read-only.)