public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ravikiran G Thirumalai <kiran@scalex86.org>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] x86_64: x86-64 mailing lists / posting patchkits / x86-64 releases
Date: Mon, 12 Jun 2006 16:33:31 -0700	[thread overview]
Message-ID: <20060612233331.GA3924@localhost.localdomain> (raw)
In-Reply-To: <200606121307.54556.ak@suse.de>

On Mon, Jun 12, 2006 at 01:07:54PM +0200, Andi Kleen wrote:
> 
> Hallo,
> 
> Some administrativa.
> 
> In the last time I've posted all patches I sent to Linus
> at discuss@x86-64.org at least once. I did this because this list is relatively 
> low volume and I tended to get some useful feedback from the people
> subscribed here.
> 
> However I heard some rumours that I scared people away 
> from the list with the many patches.  
> 
> I also planned to post patches more often to get better
> turnaround for reviews on changed patches.
> 
> We still have a patches@x86-64 mailing list on x86-64.org which
> is mostly unused. If I moved the big patch floods over there,
> would the people who do reviews subscribe there? Please comment.

Given a choice I prefer one list for patches and discussion.  Patches on a 
separate  list will eventually result in discussions of those patches on that 
list, and might even leave out interested parties out of the ensuing discussion.
My 2c;  If a separate patch list is needed for staging patches to mainline, it 
could be something like mm-commits - a broadcast only list by the
maintainer.

Thanks,
Kiran

  parent reply	other threads:[~2006-06-12 23:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-12 11:07 x86_64: x86-64 mailing lists / posting patchkits / x86-64 releases Andi Kleen
2006-06-12 11:18 ` [discuss] " Jan Beulich
2006-06-12 14:05 ` Chris Schlaeger
2006-06-12 23:33 ` Ravikiran G Thirumalai [this message]
2006-06-13  0:35 ` Nigel Cunningham
2006-06-13  8:02 ` Muli Ben-Yehuda
2006-06-17 17:05 ` Andrew Morton
2006-06-18  7:35   ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2006-06-12 14:11 [discuss] " Langsdorf, Mark
2006-06-12 15:44 ` Randy.Dunlap

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=20060612233331.GA3924@localhost.localdomain \
    --to=kiran@scalex86.org \
    --cc=ak@suse.de \
    --cc=discuss@x86-64.org \
    --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