public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Mingming Cao <cmm@us.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: tytso@mit.edu, linux-ext4@vger.kernel.org, sandeen@redhat.com
Subject: Re: [patch 1/8] ext4: fix MB_DEBUG format warnings
Date: Fri, 30 Nov 2007 17:20:22 -0800	[thread overview]
Message-ID: <1196472022.11479.30.camel@localhost.localdomain> (raw)
In-Reply-To: <20071130162232.f4ce14c4.akpm@linux-foundation.org>

On Fri, 2007-11-30 at 16:22 -0800, Andrew Morton wrote:
> On Fri, 30 Nov 2007 16:17:32 -0800
> Mingming Cao <cmm@us.ibm.com> wrote:
> 
> > Thanks for resending the patches. The first three patches in this series
> > were missed in the ext4 patch queue, the rest of them are already queued
> > there.  They are all in ext4 patch queue now. I will check other ext4
> > patches you plan to merge to mm tree and get them sync in ext4 tree.
> > 
> > http://repo.or.cz/w/ext4-patch-queue.git
> > git://repo.or.cz/ext4-patch-queue.git
> 
> What's all this about?  
That is the latest ext4 patch queue ( quilt format patches, not full
ext4 source tree).

> I've always been pulling
> ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/LATEST/broken-out/
> (and continuously fixing the same rejects each time).
> 
> 
Ted periodically pull patches from the latest ext4 patch queue on
repo.or.cz, after they had survive fs tests, then, release the ext4
patches on kernel.org (the one you pulled from). I believe Ted is on
vacation now.....

Mingming

      reply	other threads:[~2007-12-01  1:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 20:52 [patch 1/8] ext4: fix MB_DEBUG format warnings akpm
2007-12-01  0:17 ` Mingming Cao
2007-12-01  0:22   ` Andrew Morton
2007-12-01  1:20     ` Mingming Cao [this message]

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=1196472022.11479.30.camel@localhost.localdomain \
    --to=cmm@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    /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