From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, prarit@redhat.com,
dhowells@redhat.com, kosaki.motohiro@jp.fujitsu.com,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
sam@ravnborg.org, kyle@mcmartin.ca, tony.luck@intel.com,
trond.myklebust@fys.uio.no
Subject: Re: linux-next: build problem with nfs tree (Was: Re:
Date: Fri, 16 Jan 2009 22:51:56 +0000 [thread overview]
Message-ID: <20090116145156.ebbea173.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090117094008.5a0ce562.sfr@canb.auug.org.au>
On Sat, 17 Jan 2009 09:40:08 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Andrew,
>
> On Fri, 16 Jan 2009 14:15:57 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > y:/usr/src/git26> git-checkout linux-next
> > Switched to branch "linux-next"
> > y:/usr/src/git26> who-committed.sh ba9a5918
>
> Well that commit is from 2.6.23-rc1:
>
> commit ba9a5918c86762fa7fae353c635bb6ed5221dfb8
> Author: Douglas Thompson <dougthompson@xmission.com>
> Date: Thu Jul 19 01:50:32 2007 -0700
>
> drivers/edac: add to maintainers new info
>
> before linux-next even existed. My script only works for things in
> linux-next but not in Linus' tree ...
>
> > y:/usr/src/git26> who-committed.sh 2c3fb6b1b1a43ca089032e6523207f6687c962c1
>
> And that is one I committed myself because Linus' tree is broken.
Oh, OK, sorry, drat. Two hastily and poorly chosen test cases.
> I'll see if I can do better. What do you actually want to do?
y:/usr/src/git26> who-committed.sh bcff57c25287216221d0ff82080ac37bb081969e
ide
That ;)
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, prarit@redhat.com,
dhowells@redhat.com, kosaki.motohiro@jp.fujitsu.com,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
sam@ravnborg.org, kyle@mcmartin.ca, tony.luck@intel.com,
trond.myklebust@fys.uio.no
Subject: Re: linux-next: build problem with nfs tree (Was: Re: [mmotm][PATCH] fix ia64 build error)
Date: Fri, 16 Jan 2009 14:51:56 -0800 [thread overview]
Message-ID: <20090116145156.ebbea173.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090117094008.5a0ce562.sfr@canb.auug.org.au>
On Sat, 17 Jan 2009 09:40:08 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Andrew,
>
> On Fri, 16 Jan 2009 14:15:57 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > y:/usr/src/git26> git-checkout linux-next
> > Switched to branch "linux-next"
> > y:/usr/src/git26> who-committed.sh ba9a5918
>
> Well that commit is from 2.6.23-rc1:
>
> commit ba9a5918c86762fa7fae353c635bb6ed5221dfb8
> Author: Douglas Thompson <dougthompson@xmission.com>
> Date: Thu Jul 19 01:50:32 2007 -0700
>
> drivers/edac: add to maintainers new info
>
> before linux-next even existed. My script only works for things in
> linux-next but not in Linus' tree ...
>
> > y:/usr/src/git26> who-committed.sh 2c3fb6b1b1a43ca089032e6523207f6687c962c1
>
> And that is one I committed myself because Linus' tree is broken.
Oh, OK, sorry, drat. Two hastily and poorly chosen test cases.
> I'll see if I can do better. What do you actually want to do?
y:/usr/src/git26> who-committed.sh bcff57c25287216221d0ff82080ac37bb081969e
ide
That ;)
next prev parent reply other threads:[~2009-01-16 22:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 11:05 [mmotm][PATCH] fix ia64 build error KOSAKI Motohiro
2009-01-15 11:05 ` KOSAKI Motohiro
2009-01-15 17:35 ` Andrew Morton
2009-01-15 17:35 ` Andrew Morton
2009-01-15 17:52 ` Luck, Tony
2009-01-15 17:52 ` Luck, Tony
2009-01-16 1:49 ` linux-next: build problem with nfs tree (Was: Re: [mmotm][PATCH] Stephen Rothwell
2009-01-16 1:49 ` linux-next: build problem with nfs tree (Was: Re: [mmotm][PATCH] fix ia64 build error) Stephen Rothwell
2009-01-16 1:59 ` linux-next: build problem with nfs tree (Was: Andrew Morton
2009-01-16 1:59 ` linux-next: build problem with nfs tree (Was: Re: [mmotm][PATCH] fix ia64 build error) Andrew Morton
2009-01-16 2:49 ` linux-next: build problem with nfs tree (Was: Stephen Rothwell
2009-01-16 2:49 ` linux-next: build problem with nfs tree (Was: Re: [mmotm][PATCH] fix ia64 build error) Stephen Rothwell
2009-01-16 3:41 ` KOSAKI Motohiro
2009-01-16 3:41 ` KOSAKI Motohiro
2009-01-16 4:34 ` linux-next: build problem with nfs tree (Was: Stephen Rothwell
2009-01-16 4:34 ` linux-next: build problem with nfs tree (Was: Re: [mmotm][PATCH] fix ia64 build error) Stephen Rothwell
2009-01-16 22:15 ` linux-next: build problem with nfs tree (Was: Andrew Morton
2009-01-16 22:15 ` linux-next: build problem with nfs tree (Was: Re: [mmotm][PATCH] fix ia64 build error) Andrew Morton
2009-01-16 22:40 ` linux-next: build problem with nfs tree (Was: Stephen Rothwell
2009-01-16 22:40 ` linux-next: build problem with nfs tree (Was: Re: [mmotm][PATCH] fix ia64 build error) Stephen Rothwell
2009-01-16 22:49 ` linux-next: build problem with nfs tree (Was: Stephen Rothwell
2009-01-16 22:49 ` linux-next: build problem with nfs tree (Was: Re: [mmotm][PATCH] fix ia64 build error) Stephen Rothwell
2009-01-16 22:51 ` Andrew Morton [this message]
2009-01-16 22:51 ` Andrew Morton
2009-01-17 4:43 ` David Howells
2009-01-17 5:00 ` linux-next: build problem with nfs tree (Was: Stephen Rothwell
2009-01-17 5:00 ` linux-next: build problem with nfs tree (Was: Re: [mmotm][PATCH] fix ia64 build error) Stephen Rothwell
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=20090116145156.ebbea173.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=kyle@mcmartin.ca \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
--cc=tony.luck@intel.com \
--cc=trond.myklebust@fys.uio.no \
/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.