public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Timothy Shimmin <tes@sgi•com>
Cc: Christoph Hellwig <hch@lst•de>,
	xfs-masters@oss•sgi.com, linux-next@vger•kernel.org,
	LKML <linux-kernel@vger•kernel.org>
Subject: Re: [xfs-masters] Re: linux-next: Tree for June 24 (XFS x2)
Date: Thu, 17 Jul 2008 18:28:35 +1000	[thread overview]
Message-ID: <20080717182835.55405e63.sfr@canb.auug.org.au> (raw)
In-Reply-To: <487ED7F2.3040505@sgi.com>

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

On Thu, 17 Jul 2008 15:26:10 +1000 Timothy Shimmin <tes@sgi•com> wrote:
>
> Christoph Hellwig wrote:
> > On Fri, Jun 27, 2008 at 03:23:17PM +0200, Christoph Hellwig wrote:
> >> The tree is still messed up.  This original [XFS] commit is still there,
> >> but also a revert of it.  but no patch with the actual changes again (?)
> >>
> >> Also my patch to switch to the generic xattr code is attributed to
> >> Lachlan and appears twice in the commit list.  I think this whole git
> >> tree needs to be regenerated.
> > 
> > Could this please get fixed before the 2.6.27 pull?  The xfs.git tree
> > now has Linus' latest changes pulled but this still doesn't look
> > fixed up.
> 
> Yep, I believe Lachlan is planning to regenerate the xfs git tree before
> the pull request.

When that happens, could you please make sure that the linux-next tree is
updated as well ... I have had a couple of trees where what was merged to
Linus did not match what is in linux-next - and that causes me no end of
pain when I have to merge the two ...

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-07-17  8:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24  7:56 linux-next: Tree for June 24 Stephen Rothwell
2008-06-24 11:51 ` [BUG] linux-next: Tree for June 24 - kernel panic at tg3_reset_hw() on x86_64 Kamalesh Babulal
     [not found] ` <20080624175612.cdf29651.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2008-06-24 17:53   ` [BUILD-FAILURE] linux-next: Tree for June 24 - missing files in drivers/media/dvb/ Kamalesh Babulal
2008-06-25  3:28     ` Stephen Rothwell
2008-06-25  3:48       ` Stephen Rothwell
2008-06-29 11:43         ` Mauro Carvalho Chehab
2008-06-29 12:35           ` Stephen Rothwell
2008-06-25  3:31     ` Stephen Rothwell
2008-06-25  0:18 ` linux-next: Tree for June 24 (XFS x2) Randy Dunlap
2008-06-25  0:37   ` [xfs-masters] " Dave Chinner
2008-06-25  1:31     ` Timothy Shimmin
2008-06-25  1:52       ` Timothy Shimmin
2008-06-26  8:17         ` Christoph Hellwig
2008-06-27  7:26         ` Stephen Rothwell
2008-06-25  2:01     ` Lachlan McIlroy
2008-06-25  3:43       ` Dave Chinner
2008-06-27 13:23     ` Christoph Hellwig
2008-07-16  7:19       ` Christoph Hellwig
2008-07-17  5:26         ` Timothy Shimmin
2008-07-17  8:28           ` Stephen Rothwell [this message]
2008-06-27 13:20   ` Christoph Hellwig
2008-06-25  0:24 ` linux-next: Tree for June 24 (ivtv) Randy Dunlap
2008-06-25  6:05   ` Hans Verkuil

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=20080717182835.55405e63.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=hch@lst$(echo .)de \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=tes@sgi$(echo .)com \
    --cc=xfs-masters@oss$(echo .)sgi.com \
    /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