On Thu, 8 Sep 2005, Andrew Morton wrote:
> Linus Torvalds <[EMAIL PROTECTED]> wrote:
> >
> > If you remember/save the good/bad commit ID's, you can restart the whole
> > process and just feed the correct state for the ID's:
> >
> > git bisect start
> > git bisect bad v2.6.13-rc5
> >
Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
> If you remember/save the good/bad commit ID's, you can restart the whole
> process and just feed the correct state for the ID's:
>
> git bisect start
> git bisect bad v2.6.13-rc5
> git bisect good v2.6.13-rc4
> .. here bisect w
>> Is there any way to make git tell exactly where between rc4 and rc5
>> each kernel is, so I can name the bzimages accordingly?
>
> You'd have to use the raw commit names, since these things don't have any
> symbolic names. You can get that by just doing
>
> cat .git/HEAD
Also, don't nam
On Mon, Aug 15, 2005 at 08:50:12AM -0700, Linus Torvalds wrote:
>
>
> On Mon, 15 Aug 2005, Helge Hafting wrote:
> >
> > Ok, I have downlaoded git and started the first compile.
> > Git will tell when the correct point is found (assuming I
> > do the "git bisect bad/good" right), by itself?
>
> Y
On Mon, Aug 15, 2005 at 08:50:12AM -0700, Linus Torvalds wrote:
> > Is there any way to make git tell exactly where between rc4 and rc5
> > each kernel is, so I can name the bzimages accordingly?
>
> You'd have to use the raw commit names, since these things don't have any
> symbolic names. You c
On Mon, 15 Aug 2005, Helge Hafting wrote:
>
> Ok, I have downlaoded git and started the first compile.
> Git will tell when the correct point is found (assuming I
> do the "git bisect bad/good" right), by itself?
Yes. You should see
Bisecting: xxx revisions left to test after this
and
On 8/15/05, Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
> On 8/12/05, Alan Cox <[EMAIL PROTECTED]> wrote:
> > On Gwe, 2005-08-12 at 12:01 +0200, Helge Hafting wrote:
> > > solveable by resizing. But the machine will occationally hang, forcing
> > > me to
> > > use the reset button. I los
On 8/12/05, Alan Cox <[EMAIL PROTECTED]> wrote:
> On Gwe, 2005-08-12 at 12:01 +0200, Helge Hafting wrote:
> > solveable by resizing. But the machine will occationally hang, forcing
> > me to
> > use the reset button. I lost my mbox file to this (from an ext3 fs, on
> > raid-1 on scsi.)
>
> Unles
Linus Torvalds wrote:
On Fri, 12 Aug 2005, Helge Hafting wrote:
at the moment. The setup is fine with 2.6.13-rc4-mm1 x86-64, no
problems there.
The problem still exists in 2.6.13-rc6. Usually, all I get is a
suddenly black display, solveable by resizing.
Is there any chance y
On Fri, 12 Aug 2005, Helge Hafting wrote:
>
> > at the moment. The setup is fine with 2.6.13-rc4-mm1 x86-64, no
> > problems there.
>
> The problem still exists in 2.6.13-rc6. Usually, all I get is a
> suddenly black display, solveable by resizing.
Is there any chance you could try bisecting
On Gwe, 2005-08-12 at 12:01 +0200, Helge Hafting wrote:
> solveable by resizing. But the machine will occationally hang, forcing
> me to
> use the reset button. I lost my mbox file to this (from an ext3 fs, on
> raid-1 on scsi.)
Unless you are using data=journal and have turned write cache off
11 matches
Mail list logo
