Re: cvs commit: src UPDATING

Brian Somers <[EMAIL PROTECTED]> wrote: > > In message Michael Reifenberger >writes: > > : Have you tried to start aviplay ( coming from ports/graphics/avifile ) or using > > : whine? > > > > Nope. > > vmware does the job too, and I believe star-of

Re: cvs commit: src UPDATING

> In message Michael Reifenberger >writes: > : Have you tried to start aviplay ( coming from ports/graphics/avifile ) or using > : whine? > > Nope. vmware does the job too, and I believe star-office. > Warner -- Brian <[EMAIL PROTECTED]>

Re: cvs commit: src UPDATING

In message Michael Reifenberger writes: : Have you tried to start aviplay ( coming from ports/graphics/avifile ) or using : whine? Nope. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the mes

Re: cvs commit: src UPDATING

On Mon, 28 May 2001, Warner Losh wrote: ... > : -current is NOT safe, by any stretch of the imagination. Kris K. and I > : have both posted numerous messages to -current about the problems we're > : having let me know if you need copies. > > I'm not having problems :-). However, I see tha

Re: cvs commit: src UPDATING

On Mon, May 28, 2001 at 10:16:46PM -0700, Doug Barton wrote: > > .UPDATING > > Log: > > Looks like -current is safe again, and has been since Friday. Alpha is in evern worse shape than x86. The statement that -current is safe is 110% wrong. To Unsubscribe: send mail

Re: cvs commit: src UPDATING

In message <[EMAIL PROTECTED]> Doug Barton writes: : Warner Losh wrote: : > : > imp 2001/05/28 21:26:44 PDT : > : > Modified files: : > .UPDATING : > Log: : > Looks like -current is safe again, and has been since Friday. : : -current is NOT safe, by a

Re: cvs commit: src UPDATING

Warner Losh wrote: > > imp 2001/05/28 21:26:44 PDT > > Modified files: > .UPDATING > Log: > Looks like -current is safe again, and has been since Friday. -current is NOT safe, by any stretch of the imagination. Kris K. and I have both posted numerou