Re: Check for integer overflow in datetime functions - Mailing list pgsql-patches

From Tom Lane
Subject Re: Check for integer overflow in datetime functions
Date
Msg-id 12164.1133457489@sss.pgh.pa.us
Whole thread Raw
In response to Re: Check for integer overflow in datetime functions  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-patches
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Tom Lane wrote:
>> Don't worry about that, I'll take care of it.  I prefer committing all
>> the branches at once when doing a multi-branch fix (less clutter in
>> the CVS logs).

> How do you do that?  I have multiple checked-out trees, I assume you do
> the same and just handle the simultaneous-ness by hand?

Well, they're not *exactly* simultaneous of course.  I set up the
modified files in each tree and then commit, commit, commit (the -F
option helps if the commit message is long).  I use cvs2cl to extract
CVS history, and it will fold together commits in different branches
if they have the same commit message and are within some time delta
of each other ... I think it's 5 minutes or so.

            regards, tom lane

pgsql-patches by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Check for integer overflow in datetime functions
Next
From: Tom Lane
Date:
Subject: Re: Check for integer overflow in datetime functions