Andrew Kolchoogin wrote:
> Hi!
>
> On Wed, Jul 17, 2002 at 07:40:47PM -0400, Garance A Drosihn wrote:
>
>
Hey all (ab)users of -current. Please try to work on getting -current
as stabilized as possible in the next few days and hold off on any
large changes until after re@ creates t
Hi!
On Wed, Jul 17, 2002 at 07:40:47PM -0400, Garance A Drosihn wrote:
>>>Hey all (ab)users of -current. Please try to work on getting -current
>>>as stabilized as possible in the next few days and hold off on any
>>>large changes until after re@ creates the Perforce branch for DP2 on
>>>Friday
At 11:42 PM +0200 7/17/02, John Angelmo wrote:
>John Baldwin wrote:
>>Hey all (ab)users of -current. Please try to work on getting -current
>>as stabilized as possible in the next few days and hold off on any
>>large changes until after re@ creates the Perforce branch for DP2 on
>>Friday.
>
>Well
John Baldwin wrote:
> Hey all (ab)users of -current. Please try to work on getting -current
> as stabilized as possible in the next few days and hold off on any
> large changes until after re@ creates the Perforce branch for DP2 on
> Friday. Of course, bug fixes can be merged from current back i
John Baldwin wrote:
> Of course, bug fixes can be merged from current back into the
> DP2 branch before DP2 goes out if needed, but we'd like to try and get
> it as close to right as possible the first time. :)
A working fsck would surely be a good thing for DP2. :) See thread on
current@.
Reg
Hey all (ab)users of -current. Please try to work on getting -current
as stabilized as possible in the next few days and hold off on any
large changes until after re@ creates the Perforce branch for DP2 on
Friday. Of course, bug fixes can be merged from current back into the
DP2 branch before DP
