Hi,
On 07/07/2010 08:31 PM, Andrew Dunstan wrote:
Personally I favor leaving the expanded keywords in what we import, so
that there's an exact mapping between what's in the final CVS repo and
what's in the inital git repo, and then removing them entirely. I don't
see that having old keyword expansions in the historical changesets is a
bid deal. Nobody is going to base patches on them (I hope).
Sorry for being somewhat late on this discussion.
Another reason keeping the expanded keywords in historic revisions that
hasn't been raised so far is, that they can easily be un-expanded with a
script. But it's a lot harder to do the expansion, once you are on git,
if you once happen to need that info.
Of course, I'd also remove the keywords from every (active?) branch as a
first commit after the import. I'd even favor removing those lines
completely, just as sort of a cleanup commit. And no, that shouldn't
pose any problem with outstanding patches, except you are fiddling with
the tag itself. In which case you deserve to get a conflict. ;-)
Regards
Markus Wanner
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
