Robert Haas wrote:
> On Tue, Aug 10, 2010 at 2:43 PM, Kevin Grittner
>> While we're on the topic of CF app enhancements, I often wished
>> that the date of the last change to the "Reviewers" column would
>> show underneath the name(s) where the value was not empty and the
>> date was later than
On Tue, Aug 10, 2010 at 2:43 PM, Kevin Grittner
wrote:
> Very nice. I was going to ask to have "Ready for Committer" split
> out to its own section, but with this filtering, it's probably not
> worth the bother. This change will be very nice for CF managers.
Glad you like.
> While we're on the
Robert Haas wrote:
> While I was at it, I implemented a feature I've been wanting for a
> while: I made the "Status Summary" line at the top of the
> CommitFest page have links to filter by status.
Very nice. I was going to ask to have "Ready for Committer" split
out to its own section, but w
Tom Lane wrote:
> Hm, looks like you went for a one-week timeout?
> That'll be an improvement for me, I expect, but maybe not for
> other people. Should it be longer?
The longer the setting, the more convenient for me, but I have a
hard time getting work up over logging in once per week. :-)
Robert Haas writes:
> On Tue, Aug 10, 2010 at 1:22 PM, Tom Lane wrote:
>> Anyway, maybe setting a normal expires date will make it work better.
> Done.
[ logs in again ... ] Hm, looks like you went for a one-week timeout?
That'll be an improvement for me, I expect, but maybe not for other
peop
On Tue, Aug 10, 2010 at 1:22 PM, Tom Lane wrote:
> Thom Brown writes:
>> On 10 August 2010 16:26, Robert Haas wrote:
>>> I don't see how that's possible, unless your browser is eating cookies
>>> for breakfast. There's no code anywhere in the application to (a)
>>> remove cookies from the datab
Thom Brown writes:
> On 10 August 2010 16:26, Robert Haas wrote:
>> I don't see how that's possible, unless your browser is eating cookies
>> for breakfast. There's no code anywhere in the application to (a)
>> remove cookies from the database or (b) refuse to use cookies that are
>> in the data
On 10 August 2010 16:26, Robert Haas wrote:
> On Tue, Aug 10, 2010 at 11:22 AM, Tom Lane wrote:
>> "Kevin Grittner" writes:
>>> Tom Lane wrote:
$SUBJECT seems to be less than 12 hours, which is annoyingly
short. I don't see a good reason why I should have to log in
again every m
On Tue, Aug 10, 2010 at 11:22 AM, Tom Lane wrote:
> "Kevin Grittner" writes:
>> Tom Lane wrote:
>>> $SUBJECT seems to be less than 12 hours, which is annoyingly
>>> short. I don't see a good reason why I should have to log in
>>> again every morning. I could see expiring the cookie in a week o
"Kevin Grittner" writes:
> Tom Lane wrote:
>> $SUBJECT seems to be less than 12 hours, which is annoyingly
>> short. I don't see a good reason why I should have to log in
>> again every morning. I could see expiring the cookie in a week or
>> so, or tying it to a particular IP address, but this
Robert Haas wrote:
> it just sets a cookie that lasts
> for the lifetime of your browser session.
Ah, that's probably the difference -- I don't close the browser
window with the CF app. I just lock my workstation.
-Kevin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
Robert Haas writes:
> On Tue, Aug 10, 2010 at 10:48 AM, Tom Lane wrote:
>> $SUBJECT seems to be less than 12 hours, which is annoyingly short.
>> I don't see a good reason why I should have to log in again every
>> morning. I could see expiring the cookie in a week or so, or tying
>> it to a par
Tom Lane wrote:
> $SUBJECT seems to be less than 12 hours, which is annoyingly
> short. I don't see a good reason why I should have to log in
> again every morning. I could see expiring the cookie in a week or
> so, or tying it to a particular IP address, but this is just
> getting in the way.
On Tue, Aug 10, 2010 at 10:48 AM, Tom Lane wrote:
> $SUBJECT seems to be less than 12 hours, which is annoyingly short.
> I don't see a good reason why I should have to log in again every
> morning. I could see expiring the cookie in a week or so, or tying
> it to a particular IP address, but thi
$SUBJECT seems to be less than 12 hours, which is annoyingly short.
I don't see a good reason why I should have to log in again every
morning. I could see expiring the cookie in a week or so, or tying
it to a particular IP address, but this is just getting in the way.
rega
15 matches
Mail list logo
