Re: Some git conversion issues

Magnus Hagander wrote:
> Working on the git conversion with keywords, and I've noticed a couple of
> strange things that don't come up the same way in git. All of these are in
> non-code files, but they do defeat the "identical tarball" mode.
> 
> For example, a number of files have commits showing up in cvs with nothing at
> all changed. This triggered an update of the keywords only, with no contents
> changed.
> 
> For example, look at:
> http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/Attic/FAQ_AIX.diff?r1=1.19.2.9;r2=1.19.2.10
> http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/Attic/FAQ_HPUX.diff?r1=1.14.2.9;r2=1.14.2.10
> http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/Attic/FAQ_Solaris.diff?r1=1.22.2.10;r2=1.22.2.11
> 
> Some show up as completely empty, like:
> http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/generate_history.pl.diff?r1=1.1;r2=1.1.2.1
> 
> 
> Does anybody know how this can even happen? Wouldn't cvs normally just
> not commit the file if there are no changes?

I have reproduced this by modifying just the CVS tag:
$PostgreSQL: pgsql/src/backend/catalog/README,v 1.15 2010/07/2018:38:53 momjian Exp $

so it is possible, and can be ignored.

--  Bruce Momjian          http://momjian.us EnterpriseDB                             http://enterprisedb.com
 + None of us is going to be here forever. +