On Sun, 23 May 2010 15:53:57 -0700 "J.C. Roberts"
wrote:
> Since it seems I'm the first to find a problem with the '-D' flag, I'm
> testing to see if it is being caused by my using the ISO date_spec
> format by doing a similar checkout with the "Internet" date_spec
> format. i.e.
>
> # rm -
On Sun, 23 May 2010 17:19:03 +0100 Owain Ainsworth
wrote:
> On Sun, May 23, 2010 at 10:15:21AM -0600, Ted Roby wrote:
> > On Sun, May 23, 2010 at 9:55 AM, Owain Ainsworth
> > wrote:
> >
> > >
> > >
> > >
> > > You mean that the build failed? or that the corruption happened?
> > >
> > >
> > I mean
On Sun, May 23, 2010 at 10:15:21AM -0600, Ted Roby wrote:
> On Sun, May 23, 2010 at 9:55 AM, Owain Ainsworth wrote:
>
> >
> >
> >
> > You mean that the build failed? or that the corruption happened?
> >
> >
> I mean the Xenocara and kernel builds fail, depending.
> I have used 'log' to replace i91
On Sun, May 23, 2010 at 9:55 AM, Owain Ainsworth wrote:
>
>
>
> You mean that the build failed? or that the corruption happened?
>
>
I mean the Xenocara and kernel builds fail, depending.
I have used 'log' to replace i915_drv.h when it was changed as well.
I got lucky catching the April 24 snapsh
On Sun, May 23, 2010 at 09:09:56AM -0600, Ted Roby wrote:
> On Tue, May 18, 2010 at 5:45 PM, Owain Ainsworth wrote:
>
> >
> > Can you please use cvs to bisect which commit caused the problem? (it is
> > only three commits, will not take long). It may help me fix it to know
> > what caused it.
> >
On Tue, May 18, 2010 at 5:45 PM, Owain Ainsworth wrote:
>
> Can you please use cvs to bisect which commit caused the problem? (it is
> only three commits, will not take long). It may help me fix it to know
> what caused it.
>
>
Sorry for the late reply.
I can confirm the following:
The problem d
