Magnus Hagander wrote: > > I have reproduced this by modifying just the CVS tag: > > > > ? ? ? ?$PostgreSQL: pgsql/src/backend/catalog/README,v 1.15 2010/07/20 > > ? ? ? ?18:38:53 momjian Exp $ > > To clarify with what Bruce said on IM to me, the situation is when the > workflow is to manually copy a file from one repo to another before > committing (a working one vs the committer one for example), it may > not be up to date on the version id. Personally this never happens > because I move files by making "cvs diff" in one and applying in the > other, not copying the files. > > For one thing, this showed up in a lot of .po files for 8.1.0RC1. > Peter, can you comment on if this coincides with the tools you use to > do those things? > > > > so it is possible, and can be ignored. > > Yeah, but do we want to? It means a git checkout of the branch tip > will be slightly different - in keywords only - from the previous > checkout in cvs. >
Well, we are planning to remove these tags in git anyway, and I don't think anyone cares about those tags not being consistent. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + None of us is going to be here forever. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
