From: Jan Kara <jack@suse.cz>
To: "Jérémy Cochoy" <jeremy.cochoy@gmail.com>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.cz>, Pavel Machek <pavel@suse.cz>,
Al Viro <viro@zeniv.linux.org.uk>,
ronny.pretzsch@dfs.de, Corentin Chary <corentin.chary@gmail.com>
Subject: Re: [PATCH] fs/ext2: ext2_readdir comment about returns
Date: Mon, 30 Nov 2009 12:17:56 +0100 [thread overview]
Message-ID: <20091130111755.GB4240@quack.suse.cz> (raw)
In-Reply-To: <a229bc400911291530s51e1971do402e6441115d70ee@mail.gmail.com>
Hello,
On Mon 30-11-09 00:30:55, Jérémy Cochoy wrote:
> From:Jeremy Cochoy <jeremy.cochoy@gmail.com>
> I submit a short correction about a comment in ext2/dir.c
>
> (I've already send it but it wasn't the good patch format and i didn't
> cc the right people.)
>
> PS: Please excuse me if I make mistakes with the netiquette, it's my
> first patch and i wich to send more useful patchs next time, without
> hurting your eyes.
Thanks for the patch. I'd like to point you to the
Documentation/SubmittingPatches document where is described how a proper
patch submission should look like. Most importantly I miss a Signed-off-by
line (item 12 in the document) - without it the patch cannot be merged.
Also your description in the subject is inaccurate. In my opinion it should
rather be:
ext2: Fixup description of ext2_find_entry
Finally, it's easier to handle submitted patches with git tools when the
body of email looks like:
Something I want in the changelog additionally to mail subject line
(probably empty in your case).
---
Something that I want to say but should not end up in the changelog.
Patch.
Seeing that you have probably generated your patch from git, git
format-patch and git send-email are useful commands for submitting patches
via email.
Honza
prev parent reply other threads:[~2009-11-30 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-29 23:30 Jérémy Cochoy
2009-11-30 11:17 ` Jan Kara [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=20091130111755.GB4240@quack.suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=corentin.chary@gmail.com \
--cc=jeremy.cochoy@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=ronny.pretzsch@dfs.de \
--cc=viro@zeniv.linux.org.uk \
/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®