All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Satyam Sharma <satyam@infradead.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	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:56:10 -0500	[thread overview]
Message-ID: <200708311356.10826.rob@landley.net> (raw)
In-Reply-To: <alpine.LFD.0.999.0708311705270.7173@enigma.security.iitk.ac.in>

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
echo "Signed-off-by: Rob Landley <rob@landley.net>"
echo "---"
echo
cat $1 | diffstat
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...

I've got another dozen of these patches to send, but I'm waiting to see which 
ones Jesper Juhl has queued up first. :)

(Between the two of us, we'll get this updated eventually...)

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

  reply	other threads:[~2007-08-31 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 19:46 [PATCH] Documentation/00-INDEX notice ecryptfs.txt moved 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 [this message]
2007-08-31 20:13         ` Randy Dunlap

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=200708311356.10826.rob@landley.net \
    --to=rob@landley.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.