mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: stable@kernel.org
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [cebbert@redhat.com: Re: Ext4 tree backports for 2.6.27.13 and 2.6.28.2]
Date: Mon, 16 Feb 2009 18:01:04 -0500	[thread overview]
Message-ID: <20090216230104.GG23758@mini-me.lan> (raw)

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

Hi,

Can you please include the patches found in the for-stable and
for-stable-2.6.27 branches at:

	  git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git

into the next 2.6.28.y and 2.6.27.y kernels, respectively?

Or do you need me to send them in e-mail format via git
format-patch/git send-email?  I can do that too if you prefer that.

		 	      	       - Ted




[-- Attachment #2: Type: message/rfc822, Size: 2476 bytes --]

From: Chuck Ebbert <cebbert@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Ext4 tree backports for 2.6.27.13 and 2.6.28.2
Date: Mon, 16 Feb 2009 16:35:07 -0500
Message-ID: <20090216163507.1e73f452@dhcp-100-2-144.bos.redhat.com>

On Thu, 12 Feb 2009 16:19:35 -0500
Theodore Tso <tytso@mit.edu> wrote:

> 
> I've updated the for-stable and for-stable-2.6.27 branches against the
> latest stable releases, and I've updated the two flawed backports in
> the for-stable-2.6.27 branch.  Could you do a quick double-check and
> make sure the fixes are as you expect, before I send a pull request to
> stable@kernel.org?

The 2.6.27 branch looks good to me.

             reply	other threads:[~2009-02-16 23:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 23:01 Theodore Tso [this message]
2009-02-17  3:15 ` [stable] " Greg KH

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=20090216230104.GG23758@mini-me.lan \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    /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

Powered by JetHome