Re: Short CVS question - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Short CVS question
Date
Msg-id 603c8f070811080852i7cb9e469v4944259eab971e52@mail.gmail.com
Whole thread Raw
In response to Short CVS question  (Dirk Riehle <dirk@riehle.org>)
List pgsql-hackers
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

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.
>
> Thanks!
>
> Dirk
>
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>


pgsql-hackers by date:

Previous
From: "Hitoshi Harada"
Date:
Subject: Re: Windowing Function Patch Review -> Standard Conformance
Next
From: Greg Sabino Mullane
Date:
Subject: Re: FWD: Re: Updated backslash consistency patch