Short CVS question

On Fri, Nov 7, 2008 at 8:24 PM, Dirk Riehle <dirk@riehle.org> wrote:

Hi,

I have a short CVS question please: How do I go from a particular file
revision like

pgsql/cvs/pgsql/src/backend/parser/parse_relation.c.1.3

to the complete commit? I.e. I would like to navigate back from this
particular file to the commit and see all the other files that were touched
by the commit.

You can't, very easily. Every file commit in CVS is an independent
action--they are not grouped as a changeset. You would have to look
for other file commits that happened at the same time and have the
same log message. Each file has its own revision number that has no
relation to those of other files.

-Doug

In general, this is pretty hard to do in CVS - you basically have to
look for other commits with the same time stamp and log message, and I
don't think the tool provides any real support for that.

In the case of pgsql, you might want to look at the commit message and
then google the pgsql-committters mailing list archives... for
example I just found where my TRUNCATE patch was applied by googling
this:

site:archives.postgresql.org/pgsql-committers/ truncate

Note that sometimes one commit generates multiple messages in the
archives, and other times not, so you may want to look at the date or
thread index.

...Robert

Dirk Riehle wrote:

I have a short CVS question please: How do I go from a particular file
revision like

pgsql/cvs/pgsql/src/backend/parser/parse_relation.c.1.3

to the complete commit?

Also try cvs2cl, which might help you:

common_args="--revisions --no-indent --no-wrap --separate-header"
branch_arg=""
branch=$(cvs status configure.in | grep 'Sticky Tag' | awk '{print $3}')
if [ $branch != "(none)" ]; then
branch_arg="--follow $branch"
fi
if [ ! -f ChangeLog ]; then
cvs2cl $common_args $branch_arg
else
cvs2cl $common_args $branch_arg --accum
fi

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.