From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: Linux Kernel Development <linux-kernel@vger•kernel.org>,
linux-next@vger•kernel.org
Subject: Diagnosing linux-next (Was: Re: m68k libc5 regression)
Date: Sun, 1 Jun 2008 23:26:38 +1000 [thread overview]
Message-ID: <20080601232638.fda1f3ab.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080601005338.3affe880.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
Hi Andrew,
On Sun, 1 Jun 2008 00:53:38 -0700 Andrew Morton <akpm@linux-foundation•org> wrote:
>
> I do not know how to work out how this patch got into linux-next.
I have been wondering for a while what I can do to make figuring this out
(in general) easier. Would adding the SHA1 of the head of each tree to
the Trees file help? I could publish all the branches in my linux-next
repo - but they change daily. I guess only the git users benefit from
those suggestions.
gitk can tell you pretty easily (just find the offending commit and work
your way upward until you find a merge by me).
Other suggestions?
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next parent reply other threads:[~2008-06-01 13:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0805262226280.11902@anakin>
[not found] ` <Pine.LNX.4.64.0805270014110.6718@jikos.suse.cz>
[not found] ` <20080601005338.3affe880.akpm@linux-foundation.org>
2008-06-01 13:26 ` Stephen Rothwell [this message]
2008-06-01 21:04 ` Diagnosing linux-next (Was: Re: m68k libc5 regression) Andrew Morton
2008-06-02 0:39 ` Paul Mackerras
2008-06-02 1:06 ` Andrew Morton
2008-06-02 2:12 ` Paul Mackerras
2008-06-02 5:37 ` Andrew Morton
2008-06-02 5:49 ` Paul Mackerras
2008-06-02 6:22 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080601232638.fda1f3ab.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox