All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <aelder@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [GIT Review] xfs: 2.6.36 fixes
Date: Tue, 24 Aug 2010 17:54:58 -0500	[thread overview]
Message-ID: <1282690498.1885.74.camel@doink> (raw)
In-Reply-To: <20100824024445.GJ31488@dastard>

On Tue, 2010-08-24 at 12:44 +1000, Dave Chinner wrote:
> Folks,
> 
> Can you please cast an eye over the the tree below to check that all
> the bug fixes that need to go into 2.6.36 are there? If so, I'll
> send a pull request to Linus tomorrow.
> 
> Note that these are just the outstanding bug fixes that have been
> reviewed (as Linus has again decreed for pull requests after -rc1),
> so it not the complete set of reviewd patches that exist.
> 
> Cheers,
> 
> Dave.

All of these commits look good to me.  I will have these
and all the rest published on the oss.sgi.com tree later
this week.  I've been on vacation and have gotten behind.

Reviewed-by: Alex Elder <aelder@sgi.com>

> 
> The following changes since commit 9ee47476d6734c9deb9ae9ab05d963302f6b6150:
> 
>   Merge branch 'radix-tree' of git://git.kernel.org/pub/scm/linux/kernel/git/dgc/xfsdev (2010-08-22 19:55:14 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/dgc/xfsdev.git 2.6.36-fixes
. . .

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2010-08-24 22:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-24  2:44 [GIT Review] xfs: 2.6.36 fixes Dave Chinner
2010-08-24  9:12 ` Christoph Hellwig
2010-08-24 22:54 ` Alex Elder [this message]
2010-08-25  1:10   ` Dave Chinner
2010-08-25  4:50     ` Dave Chinner
2010-08-26  2:17       ` Alex Elder
2010-08-26  4:13         ` Dave Chinner

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=1282690498.1885.74.camel@doink \
    --to=aelder@sgi.com \
    --cc=david@fromorbit.com \
    --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 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.