mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vadim Lobanov <vlobanov@speakeasy.net>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
	haveblue@us.ibm.com, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: lkml traffic (was:: [PATCH] unify PFN_* macros)
Date: Mon, 3 Apr 2006 10:45:28 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0604031043410.18409@shell3.speakeasy.net> (raw)
In-Reply-To: <20060403171113.GB29351@linux-mips.org>

On Mon, 3 Apr 2006, Ralf Baechle wrote:

> On Mon, Apr 03, 2006 at 08:39:40AM -0700, Randy.Dunlap wrote:
>
> > On Mon, 3 Apr 2006 13:49:16 +0100 Ralf Baechle wrote:
> >
> > > How about posting such stuff to linux-arch?  No sane person follows l-k.
> >
> > Can we do anything about lkml?  It "doesn't scale."
>
> Not terribly much other than carefully choosing the right addresses of
> people and lists to post to.  The only thing that's worse than too much
> email is no email ...

Good choices for e-mail subjects also help quite a lot. That way, you
can quickly skim and delete all the stuff you're not interested in.
Thankfully, most of the messages on the list are good in this regard.

>   Ralf

Vadim Lobanov

  reply	other threads:[~2006-04-03 17:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23 16:24 [PATCH] unify PFN_* macros Dave Hansen
2006-04-03 12:49 ` Ralf Baechle
2006-04-03 15:39   ` lkml traffic (was:: [PATCH] unify PFN_* macros) Randy.Dunlap
2006-04-03 17:11     ` Ralf Baechle
2006-04-03 17:45       ` Vadim Lobanov [this message]
2006-04-03 21:12       ` Andrew Morton
2006-04-03 23:11         ` Ralf Baechle
2006-04-03 17:48     ` Dave Hansen
2006-04-03 15:56   ` [PATCH] unify PFN_* macros Dave Hansen
     [not found] ` <mailman.1144068720.22604.linux-kernel2news@redhat.com>
2006-04-04  5:00   ` Pete Zaitcev

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.58.0604031043410.18409@shell3.speakeasy.net \
    --to=vlobanov@speakeasy.net \
    --cc=akpm@osdl.org \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=rdunlap@xenotime.net \
    /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®