linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: bcrl@kvack.org, linux-mm@kvack.org
Subject: Re: linux-mm remailer eats [PATCH xx/yy] subject lines?
Date: Fri, 23 Jun 2006 12:40:32 -0700	[thread overview]
Message-ID: <20060623124032.5fdf6a2c.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606231207310.7483@schroedinger.engr.sgi.com>

> Paul, could sendpatchset prevent this [two subj/from headers]?

I don't think sendpatchset can prevent this.

I can't reproduce the problem, and I am guessing that the merged
headers occurred further down the email chain than sendpatchset.

I just used sendpatchset to send myself a message that had Subject:
and From: lines in the first two lines of the message.  I received
the message with those two lines still correctly in the body (after
the blank line that ends the email headers).

If someone else knows how to reproduce this problem, then we'll have
to debug it from there.

I rather doubt that its sendpatchset that is doing this.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-06-23 19:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 18:43 Christoph Lameter
2006-06-23 18:58 ` Benjamin LaHaise
2006-06-23 19:00   ` Christoph Lameter
2006-06-23 19:05     ` Benjamin LaHaise
2006-06-23 19:10       ` Christoph Lameter
2006-06-23 19:40         ` Paul Jackson [this message]
2006-06-23 19:06     ` Christoph Lameter
2006-06-23 19:08       ` Benjamin LaHaise

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=20060623124032.5fdf6a2c.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=bcrl@kvack.org \
    --cc=clameter@sgi.com \
    --cc=linux-mm@kvack.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