On Thu, 2 Nov 2000, Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > I do have a question -- just how much configuration (and other) changes
> > occurred to REL7_0_PATCHES (since the logs seem to not be telling the
> > whole story)?
> > I say this because I found at least one such cha
Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > I say this because I found at least one such change -- REL7_0_PATCHES,
> > unlike 7.0.2, has an '--enable-syslog' configure switch.
> That's probably the only one, since by back-patching it Marc was
> violating one of our standard rule
Lamar Owen <[EMAIL PROTECTED]> writes:
> I do have a question -- just how much configuration (and other) changes
> occurred to REL7_0_PATCHES (since the logs seem to not be telling the
> whole story)?
> I say this because I found at least one such change -- REL7_0_PATCHES,
> unlike 7.0.2, has an '
Peter Eisentraut wrote:
>
> Bruce Momjian writes:
> > And am seeing entries like below. Can someone please explain why I am
> > seeing stuff committed in current?
> You might want to check out cvs2cl
> (http://www.red-bean.com/kfogel/cvs2cl.shtml). It sems to work nicely and
> you get much ni
I have received no replies to this question, so I am assuming there is
no way to do this in CVS. I will dump out the branch logs in date order
and just grab the post-7.0.2 stuff. I will look at cvs2cl for 7.1.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTEC
I seem to have trouble again getting cvs logs for just the 7.0.X branch.
I am running this command from a cvs checkout tree of 7.0.X:
$ cvs log -d'>2000-06-07 00:00:00 GMT' -rREL7_0_PATCHES
And am seeing entries like below. Can someone please explain why I am
seeing stuff committed in c
