Re: cvs to git migration - keywords - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: cvs to git migration - keywords
Date
Msg-id 4C348DEA.9010702@dunslane.net
Whole thread Raw
In response to cvs to git migration - keywords  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers

Magnus Hagander wrote:
> In the previous discussions of how to migrate from cvs to git, we've
> all agreed we should kill the keyword expansion that we have now. I
> don't think, however, that we ever decided what to do with the *old*
> keywords. We did say we want to be able to reproduce backbranches/tags
> *identically* to what they are now, which indicates we need to leave
> the keywords in for those. That has other drawbacks, though.
>
> The way I see it, we have two ways to do it:
>
>
> 1) We can migrate the repository with the keywords, and then make one big
> commit just after (or before, that doesn't make a difference) removing
> them. In this case, backbranches and tags look exactly like they do
> now, but it also means if you do "git diff" between old versions, the
> keywords will show up there.
>   

I don't think this would be a terrible tragedy. Import, remove keyword 
lines on live branches, commit. That's what I'd do.

cheers

andrew




pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: Proposal for 9.1: WAL streaming from WAL buffers
Next
From: Tom Lane
Date:
Subject: Re: cvs to git migration - keywords