From: Nick Andrew <nick@nick-andrew.net>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Roman Zippel <zippel@linux-m68k.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix incorrect use of loose in hfs.txt
Date: Tue, 6 Jan 2009 01:58:49 +1100 [thread overview]
Message-ID: <20090105145849.GA19272@mail.local.tull.net> (raw)
In-Reply-To: <20081222110633.ea77cad9.randy.dunlap@oracle.com>
On Mon, Dec 22, 2008 at 11:06:33AM -0800, Randy Dunlap wrote:
> For any of these patches that were not picked up/merged/applied by someone,
> maybe you should resend them to lkml/wherever and cc: trivial@kernel.org:
Yes, I'll check again in a couple of months. More recently I posted
a bunch of typo fixes to lkml + trivial and that's a lot easier for
me to do than sending each patch to a maintainer. Any patch which
fails to merge due to real work in an affected file can be dropped
and resubmitted later.
Nick.
prev parent reply other threads:[~2009-01-05 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 3:07 Nick Andrew
2008-12-22 19:06 ` Randy Dunlap
2009-01-05 14:58 ` Nick Andrew [this message]
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=20090105145849.GA19272@mail.local.tull.net \
--to=nick@nick-andrew.net \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--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
all inboxes | Powered by JetHome®