Greg Black wrote:
Sergey Babkin wrote:
There are other things which may not allow a job to finish in
a predefined time slot. For example, other operations going on
and consuming CPU, disk or network bandwidth. So presuming
that a job would finish by some time is inherently unsafe.
To mention it from the start, I've backed out my changes.
(Yes, the pre-backed-out version was the one with the old behavior
enabled by default and changed behavior enabled by an option).
Doug Barton wrote:
On Sun, 21 Jan 2001, Sergey Babkin wrote:
Doug Barton wrote:
This
Sergey Babkin wrote:
To mention it from the start, I've backed out my changes.
Thank you.
There are other things which may not allow a job to finish in
a predefined time slot. For example, other operations going on
and consuming CPU, disk or network bandwidth. So presuming
that a job
On Sun, Jan 21, 2001 at 07:33:43PM -0800, Doug Barton wrote:
You need to back out your changes and let the people who are
proposing a more complete solution which has been widely discussed and
agreed to have time to finish their work and send it to -arch for more
discussion. Your
Doug Barton wrote:
This needs to be backed out immediately. This isn't even close to what was
discussed in -hackers. After LONG, often pointless discussion, the
following points were agreed to there.
Could you please look at the changes first ? The changes I
committed are _not_
On Sun, 21 Jan 2001, Sergey Babkin wrote:
Doug Barton wrote:
This needs to be backed out immediately. This isn't even close to what was
discussed in -hackers. After LONG, often pointless discussion, the
following points were agreed to there.
Could you please look at the
6 matches
Mail list logo
