From: Jeff Garzik <jgarzik@pobox.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
sfrench@samba.org
Subject: Re: fix oops in build_wildcard_path_from_dentry
Date: Tue, 13 Jul 2004 10:38:09 -0400 [thread overview]
Message-ID: <40F3F3D1.5090705@pobox.com> (raw)
In-Reply-To: <200407130806.i6D86NdD009894@hera.kernel.org>
Linux Kernel Mailing List wrote:
> ChangeSet 1.1819, 2004/07/07 07:27:18-05:00, stevef@steveft21.ltcsamba
>
> fix oops in build_wildcard_path_from_dentry
Would you mind adding a prefix that makes it clear what this changeset
entry is actually referring to? My recommendation would be "[CIFS] ".
The casual changelog or bk-commits-head reader has no idea that this
change (and similar cifs changes from you) is related to CIFS without
opening the message or extracting the changeset -- which defeats the
purpose of the changelog/email subject.
Jeff
parent reply other threads:[~2004-07-13 14:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200407130806.i6D86NdD009894@hera.kernel.org>]
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=40F3F3D1.5090705@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@samba.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