Tom Lane escribió:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
> > There's another issue which is that of the $Id$ and similar tags. We
> > have to decide what we want to do with them. If we're not going to have
> > them in the Git repository, then they are only causing trouble right now
> > and it would be better to get rid of them completely for the conversion,
> > to avoid the noise that they will invariably cause.
>
> What was in the back of my mind was that we'd go around and mass-remove
> $PostgreSQL$ (and any other lurking tags), but only from HEAD and only
> after the repo conversion. Although just before it would be okay too.
> The stickier part of this is what to do about back branches;
> particularly whether we are okay with checked-out versions of past
> releases not matching the actual shipped tarballs on this point.
You mean we would remove them from CVS? I don't think that's
necessarily a good idea; it'd be massive changes for no good reason. My
idea was to remove them from the repository that would be used for the
conversion (I think that means editing the ,v files), and not put that
change back to the "real" CVS repo. Then the conversion to Git gets a
lot simpler; and the checking of this modified repo against copies
checked out from Git would be simpler.
Since this change is supposed to be scriptable, the script should be
available so potential testers of the conversion can get a converted
repository too. (Or maybe we should just provide access to the modified
copy of the repo).
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support