All of lore.kernel.org
 help / color / mirror / Atom feed
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:15:57 +0000	[thread overview]
Message-ID: <20090116141557.0a3eaaac.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090116153417.891297ca.sfr@canb.auug.org.au>

On Fri, 16 Jan 2009 15:34:17 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> With the help of Paul Mackerras, I have come up with the shell script
> below.  You run it with the commit id, the tag of the tree you care
> about (e.g. next-20080115)(it defaults to the current top of tree) and
> the name of the branch the represents Linus' tree (default to
> origin/master).  It will spit out the (or a) tree that contains the
> commit you asked about.

hm.  Thanks.

y:/usr/src/git26> git-checkout linux-next
Switched to branch "linux-next"
y:/usr/src/git26> who-committed.sh ba9a5918
y:/usr/src/git26> who-committed.sh 2c3fb6b1b1a43ca089032e6523207f6687c962c1
y:/usr/src/git26> 

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:15:57 -0800	[thread overview]
Message-ID: <20090116141557.0a3eaaac.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090116153417.891297ca.sfr@canb.auug.org.au>

On Fri, 16 Jan 2009 15:34:17 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> With the help of Paul Mackerras, I have come up with the shell script
> below.  You run it with the commit id, the tag of the tree you care
> about (e.g. next-20080115)(it defaults to the current top of tree) and
> the name of the branch the represents Linus' tree (default to
> origin/master).  It will spit out the (or a) tree that contains the
> commit you asked about.

hm.  Thanks.

y:/usr/src/git26> git-checkout linux-next
Switched to branch "linux-next"
y:/usr/src/git26> who-committed.sh ba9a5918
y:/usr/src/git26> who-committed.sh 2c3fb6b1b1a43ca089032e6523207f6687c962c1
y:/usr/src/git26> 

  reply	other threads:[~2009-01-16 22:15 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           ` Andrew Morton [this message]
2009-01-16 22:15             ` 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               ` linux-next: build problem with nfs tree (Was: Andrew Morton
2009-01-16 22:51                 ` linux-next: build problem with nfs tree (Was: Re: [mmotm][PATCH] fix ia64 build error) 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=20090116141557.0a3eaaac.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.