From: Andrew Morton <akpm@linux-foundation.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org
Subject: Re: Diagnosing linux-next (Was: Re: m68k libc5 regression)
Date: Sun, 1 Jun 2008 18:06:16 -0700 [thread overview]
Message-ID: <20080601180616.75d1886e.akpm@linux-foundation.org> (raw)
In-Reply-To: <18499.16693.526974.912404@cargo.ozlabs.ibm.com>
On Mon, 2 Jun 2008 10:39:17 +1000 Paul Mackerras <paulus@samba.org> wrote:
> Andrew Morton writes:
>
> > hm, I just found the `committer' line in gitk. Coulda sworn that
> > wasn't there yesterday.
>
> It was, actually. :)
>
> Seriously, if you have any suggestions about things that would make
> gitk more useful for you, let me know.
>
tkdiff-style diff viewer!
I mentioned that to you a year or two back, and you've probabably
already done it but nobody told me about it :)
next prev parent reply other threads:[~2008-06-02 1:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 20:38 m68k libc5 regression Geert Uytterhoeven
2008-05-26 22:19 ` Jiri Kosina
2008-05-29 11:03 ` Jiri Kosina
2008-05-29 11:28 ` Geert Uytterhoeven
2008-05-29 19:38 ` Geert Uytterhoeven
2008-06-02 10:28 ` Jiri Kosina
2008-06-01 7:53 ` Andrew Morton
2008-06-01 8:37 ` Geert Uytterhoeven
2008-06-01 8:48 ` Andrew Morton
2008-06-01 9:22 ` Sam Ravnborg
2008-06-01 9:41 ` Andrew Morton
2008-06-01 10:34 ` Sam Ravnborg
2008-06-01 9:56 ` Geert Uytterhoeven
2008-06-01 13:26 ` Diagnosing linux-next (Was: Re: m68k libc5 regression) Stephen Rothwell
2008-06-01 21:04 ` Andrew Morton
2008-06-02 0:39 ` Paul Mackerras
2008-06-02 1:06 ` Andrew Morton [this message]
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
2008-06-02 10:27 ` m68k libc5 regression Jiri Kosina
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=20080601180616.75d1886e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.