Bruce Momjian <[EMAIL PROTECTED]> writes:
> I guess the question is whether it is possible using cvs2cl to show only
> HEAD, and then show if the same commit message also appears in the most
> recent back branch.
It's so rare that we make a back-branch patch without a corresponding
HEAD patch that
Andrew Dunstan wrote:
> Bruce Momjian wrote:
> > Tom Lane wrote:
> >> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> > I pull activity only from HEAD, so I do not see that tag. In fact, I
> >> > use our src/tools/pgcvslog rather than cvslog.
> >>
> >> Not sure why we are maintaining our own script
Bruce Momjian wrote:
> Tom Lane wrote:
>> Bruce Momjian <[EMAIL PROTECTED]> writes:
>> > I pull activity only from HEAD, so I do not see that tag. In fact, I
>> > use our src/tools/pgcvslog rather than cvslog.
>>
>> Not sure why we are maintaining our own script when there are much
>> better thing
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I pull activity only from HEAD, so I do not see that tag. In fact, I
> > use our src/tools/pgcvslog rather than cvslog.
>
> Not sure why we are maintaining our own script when there are much
> better things out there:
> http://freshm
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I pull activity only from HEAD, so I do not see that tag. In fact, I
> use our src/tools/pgcvslog rather than cvslog.
Not sure why we are maintaining our own script when there are much
better things out there:
http://freshmeat.net/projects/cvs2cl.pl/
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > FYI, in going through the release notes, I would like to remind
> > committers that it is important to mention if the commit was backpatched
> > to any earlier release. Not only is this valuable for making the
> > release notes, but i
Bruce Momjian <[EMAIL PROTECTED]> writes:
> FYI, in going through the release notes, I would like to remind
> committers that it is important to mention if the commit was backpatched
> to any earlier release. Not only is this valuable for making the
> release notes, but it also helps people lookin
Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > FYI, in going through the release notes, I would like to remind
> > committers that it is important to mention if the commit was
> > backpatched to any earlier release.
>
> Backpatches usually happen after the commit to the head branch has been
>
Bruce Momjian wrote:
> FYI, in going through the release notes, I would like to remind
> committers that it is important to mention if the commit was
> backpatched to any earlier release.
Backpatches usually happen after the commit to the head branch has been
made, so the information is not avail
FYI, in going through the release notes, I would like to remind
committers that it is important to mention if the commit was backpatched
to any earlier release. Not only is this valuable for making the
release notes, but it also helps people looking at the commit message.
--
Bruce Momjian [E
> Question:
>
> What has changed with the CVS repository lately? I notice that all of the
> commit messages I've read lately on pgsql-committers seem to come from
> Marc Fournier. Has Marc just been committing all recent changes, or are
> all commit messages, regardless of committer, showing as f
I have to look into the commit script to see about pulling out th eproper
committer ... cvs logs show the person who did the commit, but the email's
are coming from me ...
On Sun, 9 Sep 2001, Neil Padgett wrote:
> Question:
>
> What has changed with the CVS repository lately? I notice that all
Question:
What has changed with the CVS repository lately? I notice that all of the
commit messages I've read lately on pgsql-committers seem to come from
Marc Fournier. Has Marc just been committing all recent changes, or are
all commit messages, regardless of committer, showing as from Marc?
N
13 matches
Mail list logo
