All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Neil Brown <neilb@suse.de>
Cc: dm-devel@redhat.com, matthias.kaehlcke@gmail.com
Subject: Re: + kcopyd-use-mutex-instead-of-semaphore.patch added to -mm tree
Date: Thu, 3 May 2007 23:42:00 -0700	[thread overview]
Message-ID: <20070503234200.e75eb71c.akpm@linux-foundation.org> (raw)
In-Reply-To: <17978.53701.832765.808256@notabene.brown>

On Fri, 4 May 2007 16:25:09 +1000 Neil Brown <neilb@suse.de> wrote:

> Should be
>   Cc: dm-devel@redhat.com

drat.

> Maybe there should be a Cc: line in the top of each file??

I've thought about that sometimes.  I end up adding a lot of cc's.

I _could_ just do a reverse lookup on my patches directory and work out
who I cc'ed last time on that file.

A git-whatchanged|grep would be a more accurate way.  A bit spammy though.

I have it all in my head ;)

  reply	other threads:[~2007-05-04  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04  5:52 + kcopyd-use-mutex-instead-of-semaphore.patch added to -mm tree akpm
2007-05-04  6:25 ` Neil Brown
2007-05-04  6:42   ` Andrew Morton [this message]
2007-05-04  7:09     ` Neil Brown

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=20070503234200.e75eb71c.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dm-devel@redhat.com \
    --cc=matthias.kaehlcke@gmail.com \
    --cc=neilb@suse.de \
    /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.