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>
Cc: Roman Zippel <zippel@linux-m68k.org>,
	Warren Turkal <wt@penguintechs.org>
Subject: hfsplus journal detection - next try
Date: Wed,  5 Nov 2008 23:44:21 -0800	[thread overview]
Message-ID: <1225957463-29519-1-git-send-email-wt@penguintechs.org> (raw)
In-Reply-To: <20081105140937.GA27438@infradead.org>

Here is my next stab at this issue. I refactored the logic into a function and
took out the != 0 like you all suggested. Please let me know if there is
anything else I can do to improve it.

Also, I am just getting used to git. Is the best workflow to create a branch
that I cherrypick seemingly acceptable patches into and just createa a different
branch for each patchset attempt?

Thanks,
wt

  reply	other threads:[~2008-11-06  7:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05  8:00 hfsplus journal detection Warren Turkal
2008-11-05  8:00 ` [PATCH] Identify journal info block in volume header Warren Turkal
2008-11-05  8:00   ` [PATCH] Fix journal detection on HFS+ Warren Turkal
2008-11-05 10:40     ` Jörn Engel
2008-11-05 14:09       ` Christoph Hellwig
2008-11-06  7:44         ` Warren Turkal [this message]
2008-11-06  7:44           ` [PATCH] Identify journal info block in volume header Warren Turkal
2008-11-06  7:44             ` [PATCH] Fix journal detection on HFS+ Warren Turkal
2008-11-07  8:32               ` Jörn Engel
2008-11-07 18:01                 ` Warren Turkal
2008-11-08 11:09                   ` Jörn Engel
2008-11-09  5:27                     ` Warren Turkal
2008-11-09 11:02                       ` Jörn Engel

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=1225957463-29519-1-git-send-email-wt@penguintechs.org \
    --to=wt@penguintechs.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).