linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: linux-mm@kvack.org
Subject: Re: linux-mm remailer eats [PATCH xx/yy] subject lines?
Date: Fri, 23 Jun 2006 12:00:13 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0606231159310.7339@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20060623185828.GB13617@kvack.org>

On Fri, 23 Jun 2006, Benjamin LaHaise wrote:

> On Thu, Jun 22, 2006 at 11:43:50AM -0700, Christoph Lameter wrote:
> > We noticed that many of my emails to this list have the [PATCH ...] 
> > subject part removed from it. The mails to lkml arrive just fine. The cc 
> > that I am getting is also okay. Anyone have a clue?
> 
> That shouldn't be happening unless bogofilter is catching it as spam.  The 
> few items that are marked unsure are usually approved by me within a short 
> period of time.  If you have a particular example, I can dig through the 
> logs to see what happened.

Have a look at the zoned VM counter patch V6 that was posted recently to 
linux-mm. The first two patches have the [] intact the later 12 have them 
all removed.

--
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:00 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 [this message]
2006-06-23 19:05     ` Benjamin LaHaise
2006-06-23 19:10       ` Christoph Lameter
2006-06-23 19:40         ` Paul Jackson
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=Pine.LNX.4.64.0606231159310.7339@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=bcrl@kvack.org \
    --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