linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	xfs@oss.sgi.com
Subject: Re: linux-next: left over things in linux-next after 2.6.28-c1
Date: Sun, 26 Oct 2008 04:39:39 -0400	[thread overview]
Message-ID: <20081026083939.GA19394@infradead.org> (raw)
In-Reply-To: <20081026193421.f5f7d8f1.sfr@canb.auug.org.au>

On Sun, Oct 26, 2008 at 07:34:21PM +1100, Stephen Rothwell wrote:
> Presumably what was merged was slightly different (or the commits were
> split up differently).  This is the same problem I have with the kvm tree.

It should be the same, but the xfs trees have been a bit of a maze
recently, so it shouldn't be a surprise that your list got out of sync.


  reply	other threads:[~2008-10-26  8:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-25 13:50 linux-next: left over things in linux-next after 2.6.28-c1 Stephen Rothwell
2008-10-25 13:58 ` Al Viro
2008-10-25 14:37 ` Sam Ravnborg
2008-10-25 21:16   ` Greg KH
2008-10-25 21:52     ` Sam Ravnborg
2008-10-25 22:10       ` Greg KH
2008-10-28  5:34         ` Ananth N Mavinakayanahalli
2008-10-29 23:53           ` Greg KH
2008-10-25 21:20 ` Greg KH
2008-10-25 23:48 ` Randy Dunlap
2008-10-26  0:07   ` Randy Dunlap
2008-10-26  7:40 ` Stefan Richter
2008-10-26  8:17 ` Christoph Hellwig
2008-10-26  8:34   ` Stephen Rothwell
2008-10-26  8:39     ` Christoph Hellwig [this message]
2008-10-27  7:44       ` Lachlan McIlroy

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=20081026083939.GA19394@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=xfs@oss.sgi.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).