All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Stephen Tweedie <sct@redhat.com>,
	linux-ext4@vger.kernel.org, Andreas Dilger <adilger@sun.com>
Subject: Re: A tree to pull into linux-next
Date: Thu, 16 Jul 2009 12:45:47 +0200	[thread overview]
Message-ID: <20090716104547.GA25725@duck.suse.cz> (raw)
In-Reply-To: <20090716164826.f4edbd42.sfr@canb.auug.org.au>

On Thu 16-07-09 16:48:26, Stephen Rothwell wrote:
> Hi Jan,
> 
> On Wed, 15 Jul 2009 21:37:42 +0200 Jan Kara <jack@suse.cz> wrote:
> >
> >   I've decided to create a tree through which I can occasionally merge
> > mainly ext3/JBD fixes (and possibly also fixes to filesystems which
> > don't have a maintainer). Hopefully this reduces chances that some patches
> > get lost on the way... Could you please start pulling the tree below to
> > linux-next? Thanks.
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs-2.6.git for_next
> 
> I am happy to include this, but (no offense) I would like to hear from
> the ext3 and jbd maintainers (cc'd) about it.
  Sure. BTW: Stephen Tweedie isn't doing ext3/jbd anymore for a few years
(probably we should remove him from MAINTAINERS)...

									Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2009-07-16 10:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090715193742.GA18583@duck.suse.cz>
2009-07-16  6:48 ` A tree to pull into linux-next Stephen Rothwell
2009-07-16 10:45   ` Jan Kara [this message]
2009-07-16 11:56     ` Stephen C. Tweedie
2009-07-16 11:47   ` Theodore Tso
2009-07-16 11:52     ` Jan Kara
2009-07-21  6:08       ` Stephen Rothwell
2009-07-21  6:15         ` Andrew Morton
2009-07-21  6:27           ` Stephen Rothwell

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=20090716104547.GA25725@duck.suse.cz \
    --to=jack@suse.cz \
    --cc=adilger@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sct@redhat.com \
    --cc=sfr@canb.auug.org.au \
    /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.