From: Andrew Morton <akpm@linux-foundation.org>
To: Ian Kent <raven@themaw.net>
Cc: linux-kernel@vger.kernel.org, autofs@linux.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/4] autofs4 - implement a miscelaneous device for ioctl control
Date: Mon, 25 Feb 2008 00:17:52 -0800 [thread overview]
Message-ID: <20080225001752.d154e88b.akpm@linux-foundation.org> (raw)
In-Reply-To: <1203925954.3087.64.camel@raven.themaw.net>
We have four patches, all with the same title - please avoid doing this.
I could invent titles for them (as I often have to do), but I think it
would be best if you were to do so. That way, we avoid confusion and
people who later google for the patch's title to understand the patch's
background will get better coverage.
So... resend, please?
Documentation/SubmittingPatches has some tips on all of this - search term
is "Subject:".
next parent reply other threads:[~2008-02-25 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1203925954.3087.64.camel@raven.themaw.net>
2008-02-25 8:17 ` Andrew Morton [this message]
2008-02-25 9:29 ` [PATCH 0/4] autofs4 - implement a miscelaneous device for ioctl control Ian Kent
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=20080225001752.d154e88b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=autofs@linux.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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