From: Randy Dunlap <rdunlap@xenotime.net>
To: Rob Landley <rob@landley.net>
Cc: Satyam Sharma <satyam@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Documentation/00-INDEX notice ecryptfs.txt moved.
Date: Fri, 31 Aug 2007 13:13:01 -0700 [thread overview]
Message-ID: <20070831131301.bd9e727d.rdunlap@xenotime.net> (raw)
In-Reply-To: <200708311356.10826.rob@landley.net>
On Fri, 31 Aug 2007 13:56:10 -0500 Rob Landley wrote:
> On Friday 31 August 2007 7:10:00 am Satyam Sharma wrote:
> > Hi Rob,
> >
> > On Thu, 30 Aug 2007, Rob Landley wrote:
> > > On Thursday 30 August 2007 2:04:37 pm Randy Dunlap wrote:
> > > > Please use the expected (canonical) patch format.
> > > >
> > > > See Documentation/SubmittingPatches:
> > > > 14) The canonical patch format
> > >
> > > from Rob Landley <rob@landley.net>
> > > Signed-off-by: Rob Landley <rob@landley.net>
> > >
> > > ecryptfs.txt moved into filesystems, make 00-INDEX follow.
> >
> > That's still not quite right :-) What Randy meant is that the sign-off
> > must come /after/ the patch description:
>
> Randy emailed me about it offline and I updated my wrapper script.
>
> I've always had a bit of a blind spot when it comes to filling out forms (I
> suck at bureaucracy), so I made a script to do it, currently:
>
> #!/bin/bash
>
> echo "From: Rob Landley <rob@landley.net>"
> echo
or: echo put_changelog_here
> echo "Signed-off-by: Rob Landley <rob@landley.net>"
> echo "---"
> echo
> cat $1 | diffstat
cat $1 | diffstat -p1 -w70
> echo
> cat $1
>
> I note that the example uses "From:" but the summary refers to it as
> the "from" line with no capital letter or colon, and unix being case
> sensitive I reproduced the quoted string verbatim. (See "I suck at
> bureaucracy", above.)
>
> > [ All this is not too important, admittedly, but causes least amount of
> > processing time to be wasted on the recipient's end, and also does not
> > confuse scripts that may be used to extract patches (and git commit
> > command-line arguments) from mails automatically. ]
>
> If it's going to be parsed by a script, it might as well be generated by a
> script...
yep.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2007-08-31 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 19:46 Rob Landley
2007-08-30 19:04 ` Randy Dunlap
2007-08-31 1:16 ` Rob Landley
2007-08-31 12:10 ` Satyam Sharma
2007-08-31 18:56 ` Rob Landley
2007-08-31 20:13 ` Randy Dunlap [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=20070831131301.bd9e727d.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=satyam@infradead.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®