From: | Tim Landscheidt <tim(at)tim-landscheidt(dot)de> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: cvs to git migration - keywords |
Date: | 2010-07-07 15:25:34 |
Message-ID: | m3aaq3iaa9.fsf@passepartout.tim-landscheidt.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> 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.
>> +1 for #1. Changing history and the resulting possibility of becoming
>> one's own grandfather always makes me nervous.
> Yeah. One concrete problem with removing the $PostgreSQL$ lines is it
> will affect line numbering everywhere. Yeah, it's only off-by-one, but
> there could still be confusion.
> [...]
If not the whole line was removed, but only the
"$PostgreSQL$" part, the numbering should stay the same. I
guess it would otherwise be challenging to automatically not
only delete the "$PostgreSQL$" line, but also leading and/or
trailing empty (comment) lines, and not mess up.
Tim
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Fowler | 2010-07-07 15:37:40 | [PATCH] Re: Issue: Deprecation of the XML2 module 'xml_is_well_formed' function |
Previous Message | Peter Froehlich | 2010-07-07 15:19:17 | Re: Python Interface Hacking |