public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: coly <colyli@gmail.com>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: which tree should I generate the ext4 patch ?
Date: Thu, 24 May 2007 17:02:51 +0800	[thread overview]
Message-ID: <1179997371.4353.1.camel@coly-t43.site> (raw)
In-Reply-To: <20070523121723.GC5608@thunk.org>

Theodore,

I can see all the files, but how can I download the files by cvs ? I
tried pserver, but it seems does not work ..

could you give me some hints ?

Thanks

Coly

在 2007-05-23三的 08:17 -0400,Theodore Tso写道:
> On Wed, May 23, 2007 at 05:00:43PM +0800, coly wrote:
> > 
> > These days, I am tring to post my patch for inode reservation on
> > linux-ext4. But I am confused on which tree I should generate the patch.
> > 
> > I worked on mm-tree. But now Thoedore creates a tree for ext4, so should
> > I generate the patch based on tso-tree ?
> 
> The mm-tree is fed from the ext4 patch series, so there shouldn't be
> much difference.
> 
> > Same question to e2fsprogs. I guess maybe I should generate the patch
> > for e2fsprogs based on e2fsprogs-TEST branch, a.k.a 1.40-WIP-0407. Isn't
> > it ?
> 
> Yes, or if you want to use the very latest, you can use the Mercurial
> repository located at:
> 
> 	http://thunk.org/hg/e2fsprogs
> 
> I will be switch to git at some point in the near future, probably
> after the e2fsprogs 1.40 release, but for now that's the place to get
> the very latest.  
> 
> In practice, it's not hard to rebase patches, but patches against the
> more recent versions are definitely appreciated.  So if you're not
> familiar with using Mercurial, please feel free to use the
> 1.40-WIP-0407 as the base for your patches.  
> 
> Regards, 
> 
> 					- Ted

  parent reply	other threads:[~2007-05-24  9:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23  9:00 which tree should I generate the ext4 patch ? coly
2007-05-23 12:17 ` Theodore Tso
2007-05-23 13:23   ` coly
2007-05-24  9:02   ` coly [this message]
2007-05-24  9:05     ` Aneesh Kumar K.V

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=1179997371.4353.1.camel@coly-t43.site \
    --to=colyli@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --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