linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Warren Turkal" <wt@penguintechs.org>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>
Cc: "Roman Zippel" <zippel@linux-m68k.org>,
	"Warren Turkal" <wt@penguintechs.org>
Subject: Re: hfsplus journal detection - try 4
Date: Wed, 19 Nov 2008 14:36:02 -0800	[thread overview]
Message-ID: <e37d376a0811191436x6cc45b25rf8374f13c57368cb@mail.gmail.com> (raw)
In-Reply-To: <1226437008-14247-1-git-send-email-wt@penguintechs.org>

Andrew,

I am sending this to you since it's a small patchset and I'm not
getting any traction with the alleged HFS+ maintainer. Is this small
enough to make it into 2.6.28 or will it have to wait for the next
cycle?

BTW, I am the guy who just came to your cube to bug you.

Thanks,
wt

On Tue, Nov 11, 2008 at 12:56 PM, Warren Turkal <wt@penguintechs.org> wrote:
> Here's another shot at this patch. I found a small issue with sparse.
> If this is suitable for inclusion, could someone please pull it into
> their tree so that it can be merged upstream?

  parent reply	other threads:[~2008-11-19 22:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11 20:56 hfsplus journal detection - try 4 Warren Turkal
2008-11-11 20:56 ` [PATCH] Identify journal info block in volume header Warren Turkal
2008-11-11 20:56   ` [PATCH] Fix journal detection on HFS+ Warren Turkal
2008-11-11 20:56     ` [PATCH] Fix header include Warren Turkal
2008-11-19 22:51       ` Andrew Morton
2008-11-19 23:01         ` Brad Boyer
2008-11-20  0:41         ` Brad Boyer
2008-11-20  2:30           ` Warren Turkal
2008-11-19 22:51     ` [PATCH] Fix journal detection on HFS+ Andrew Morton
2008-11-20  1:01       ` Warren Turkal
2008-11-19 22:49   ` [PATCH] Identify journal info block in volume header Andrew Morton
2008-11-19  7:07 ` hfsplus journal detection - try 4 Warren Turkal
2008-11-19  8:39   ` Jörn Engel
2008-11-19 22:36 ` Warren Turkal [this message]
2008-11-19 22:49 ` Andrew Morton

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=e37d376a0811191436x6cc45b25rf8374f13c57368cb@mail.gmail.com \
    --to=wt@penguintechs.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=zippel@linux-m68k.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).