Thread (1 message) 1 message, 1 author, 2016-06-15

Re: Real-life kernel debugging scenario

From: Jon Loeliger <hidden>
Date: 2016-06-15 22:42:11

On Wed, 2005-11-09 at 11:40, wa1ter@myrealbox.com wrote:
On Mon, 7 Nov 2005, Linus Torvalds wrote:

[...]
quoted
The way to use "git bisect" couldn't be easier.
I see that Junio just added your entire response to
Documentation/howto/
isolate-bugs-with-bisect.txt where even I could manage to find it :o)
Why, thank you. :-)

The built-in variable ORIG_HEAD isn't explained anywhere AFAICT, or at
least it wasn't until today.  Are there other such magic variables
which
might be useful for us to know about?
Hey Junio,

I'm going to call "I told you so!" on this one! :-)

Ref:
    Message-ID:  [ref]
    From: Jon Loeliger [off-list ref]
    Subject: Now What?
    Date: Wed, 2 Nov 2005 18:30:37 -0700

Where in I mumbled:

    I feel that an explanation of all of the behind-the-scripts-
    in-.git communication files is needed.  In particular these:

        FETCH_HEAD
        MERGE_HEAD
        LAST_MERGE
        MERGE_MSG

    These need to be mentioned and explained because they
    frequently form exactly the critical missing link or
    starting point after a failed fetch or merge.

You know.

jdl
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help