From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"V9FS Developers" <v9fs-developer@lists.sourceforge.net>
Subject: Re: [PULL] v9fs bug fixes and documentation updates for 2.6.26
Date: Wed, 14 May 2008 21:43:50 -0500 [thread overview]
Message-ID: <a4e6962a0805141943va8a9043k9ca3ff023bc6aa5@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0805141930530.3019@woody.linux-foundation.org>
On Wed, May 14, 2008 at 9:40 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
>
> On Wed, 14 May 2008, Eric Van Hensbergen wrote:
>>
>> Jim Meyering (1):
>> fs/9p/v9fs.c (v9fs_parse_options): Handle kstrdup and
>> match_strdup failure. Now that this function can fail, return an int,
>> diagnose other option-parsing failures, and adjust the sole caller:
>> (v9fs_session_init): Handle kstrdup failure. Propagate any new
>> v9fs_parse_options failure "up".
>
> Grr. Somebody isn't following the nice rules we have and that git
> encourages: make a commit message be a nice "one-line header" with the
> more complete explanation separated by an empty line (and with nice
> line-breaks etc).
>
Sorry boss. I had a nagging feeling I was doing the wrong thing about
not diving in and fixing that comment. Not sure where I messed up
applying the email, but if I see that sort of thing in the future I'll
edit it by hand.
>
> There are other commits that don't follow the rules, btw: you've applied
> patches from others that have the rigth Sign-off's from the authors, but
> you should sign off yourself, not just ack them. By actually taking that
> thing and committing it, you're doing more than ack'ing somebody elses
> work.
>
Sure, long term misunderstand on my part. Thanks for clearing this
up, I'll be sure to properly sign off in the future.
-eric
prev parent reply other threads:[~2008-05-15 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 2:20 Eric Van Hensbergen
2008-05-15 2:40 ` Linus Torvalds
2008-05-15 2:43 ` Eric Van Hensbergen [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=a4e6962a0805141943va8a9043k9ca3ff023bc6aa5@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=v9fs-developer@lists.sourceforge.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
all inboxes | Powered by JetHome®