public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [RESEND] The initmpfs patches.
Date: Tue, 16 Jul 2013 18:43:00 -0500	[thread overview]
Message-ID: <1374018180.3719.12@driftwood> (raw)
In-Reply-To: <CALkWK0n5GSMv0n0oqo1FZUWtYNLtJsLVhiv5EaMEebAu6T4GQQ@mail.gmail.com> (from artagnon@gmail.com on Tue Jul 16 02:12:19 2013)

On 07/16/2013 02:12:19 AM, Ramkumar Ramachandra wrote:
> Rob Landley wrote:
> > (Balsa is such an incompetent email client I wrote a python script  
> to do
> > this via raw smtp, and I'm always convinced it's going to screw up  
> the send.
> > But I think I've got it debugged now...)
> 
> Use the tried-and-tested git-send-email.perl, perhaps?

Is this script of yours any use for patches that aren't, and never  
were, in git? (Given that it's not in the kernel tree, I'm guessing  
"no".)

That said... in my resend this morning I substituted the message-id of  
the first message instead of the reply-to, didn't I? (Trying to make it  
a reply to Andrew's most recent message. Confused the list archive, it  
seems.)

I'll resend again...

Rob

  reply	other threads:[~2013-07-16 23:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10  2:06 [RESEND] The initmpfs patches Rob Landley
2013-07-15 21:01 ` Andrew Morton
2013-07-16  4:07   ` Rob Landley
2013-07-16  7:12     ` Ramkumar Ramachandra
2013-07-16 23:43       ` Rob Landley [this message]
2013-07-17  7:02         ` Ramkumar Ramachandra
2013-07-17 23:06   ` [PATCH 0/5] initmpfs v2: use tmpfs instead of ramfs for rootfs Andrew Morton
2013-07-18  0:15     ` Hugh Dickins
2013-07-18 23:17       ` Rob Landley
2013-07-18 23:59     ` H. Peter Anvin

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=1374018180.3719.12@driftwood \
    --to=rob@landley.net \
    --cc=akpm@linux-foundation.org \
    --cc=artagnon@gmail.com \
    --cc=linux-kernel@vger.kernel.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