From: Theodore Tso <tytso@mit.edu>
To: Frank Mayhar <fmayhar@google.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] Allow ext4 to run without a journal.
Date: Sat, 3 Jan 2009 20:17:47 -0500 [thread overview]
Message-ID: <20090104011747.GI4758@mit.edu> (raw)
In-Reply-To: <1231013940.22046.4.camel@bobble.smo.corp.google.com>
On Sat, Jan 03, 2009 at 12:19:00PM -0800, Frank Mayhar wrote:
> On Sat, 2009-01-03 at 10:52 -0500, Theodore Tso wrote:
> > I've modified your patch to reflect the comments I made two weeks ago.
> > Were there any other changes you have planned? I'd like to get this
> > pushed to Linus soon....
>
> My apologies, I have a new patch that has been tested quite a bit more
> (although I still wouldn't say quite thoroughly yet, but close), all I
> need to do is set it up correctly for you guys and send it to the list.
> Unfortunately other stuff (including the holidays) has gotten in the
> way. Expect it on Monday or Tuesday. Note that this version will have
> a handful of small but important bugs fixed, as well.
>
> One question: Shold I make the patch relative to the stable tree or to
> the latest bits?
At this point can you make your patch relative to whatever you used
last time (and remind me what it is)? Or, can you give me a delta
between what you did last time and what you have now that has the
fixes? The problem is that the patch touches so much of ext4 that
it's quite painful to maintain it in the ext4 patch queue --- it
either invalidates a large number of patches after the fact, or the
patch needs a huge amount of work to fix up patch conflicts if it is
applied afterwards --- and if it is placed in the middle of the patch
queue, both conditions apply.
So I will have to do a lot of fix ups either way. So unless you're
willing to pull down the ext4 patch queue, at:
git://repo.or.cz/ext4-patch-queue.git
... and worry about making it apply in place, it's probably easier for
you to give me delta's versus the last patch, and I'll integrate in
the changes by hand.
- Ted
next prev parent reply other threads:[~2009-01-04 1:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 23:54 [PATCH 1/1] Allow ext4 to run without a journal Frank Mayhar
2008-12-15 17:35 ` Frank Mayhar
2008-12-16 4:00 ` Theodore Tso
2008-12-17 6:00 ` Theodore Tso
2008-12-17 17:52 ` Frank Mayhar
2008-12-17 3:12 ` Theodore Tso
2008-12-17 17:50 ` Frank Mayhar
2009-01-03 15:52 ` [PATCH] " Theodore Tso
2009-01-03 20:19 ` Frank Mayhar
2009-01-04 1:17 ` Theodore Tso [this message]
2009-01-05 5:31 ` Theodore Tso
2008-12-18 6:51 ` [PATCH 1/1] " Andreas Dilger
2008-12-18 18:00 ` Jan Kara
2008-12-18 18:13 ` Michael Rubin
2008-12-18 18:27 ` Jan Kara
2008-12-18 18:29 ` Curt Wohlgemuth
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=20090104011747.GI4758@mit.edu \
--to=tytso@mit.edu \
--cc=fmayhar@google.com \
--cc=linux-ext4@vger.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;
as well as URLs for NNTP newsgroup(s).