Re: Hacking on PostgreSQL via GIT - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Hacking on PostgreSQL via GIT
Date
Msg-id 9610.1176750025@sss.pgh.pa.us
Whole thread Raw
In response to Re: Hacking on PostgreSQL via GIT  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Hacking on PostgreSQL via GIT
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> These files are generated (from gram.y, pgc.l and preproc.y
> respectievly) and are not present in the CVS repo, though I think they
> have been at some point.

> It's strange that other generated files (that have also been in the repo
> in the past) like preproc.h are not showing up.

The weird thing about these files is that the CVS history shows commits
on HEAD later than the file removal commit.  I don't recall if Vadim
unintentionally re-added the files before making those commits ... but
if he did, you'd think it'd have taken another explicit removal to get
rid of them in HEAD.  More likely, there was some problem in his local
tree that allowed a "cvs commit" to think it should update the
repository with copies of the derived files he happened to have.

I think this is a corner case that CVS handles in a particular way and
the tools people are using to read the repository handle in a different
way.  Which would be a bug in those tools, since CVS's interpretation
must be right by definition.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Re: IDENTITY/GENERATED v36 Re: [PATCHES] Final version of IDENTITY/GENERATED patch
Next
From: Zdenek Kotala
Date:
Subject: Re: Adjusting index special storage for pg_filedump's convenience