From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: x86_64: x86-64 mailing lists / posting patchkits / x86-64 releases
Date: Tue, 13 Jun 2006 10:35:32 +1000 [thread overview]
Message-ID: <200606131035.36012.ncunningham@linuxmail.org> (raw)
In-Reply-To: <200606121307.54556.ak@suse.de>
[-- Attachment #1: Type: text/plain, Size: 2514 bytes --]
Hi Andi et al.
On Monday 12 June 2006 21:07, 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.
I'll subscribe. (As in reply to the comment below...) I didn't know this site
or these lists existed.
Regards,
Nigel
> Also I'll probably start x86_64-* patchkit releases again. Currently
> my working dir on ftp.firstfloor.org is directly going into -mm* and
> that sometimes causes problems because it is not as well tested as it would
> be if a larger audience has run it. Also there are often non trivial
> interactions with the many patches in -mm* and it's hard to figure
> out where a problem comes from. So it looks like some separate
> testing would be better.
>
> I hope people would be still interested in running x86_64-* patchkits.
>
> Also my feeling is that I need to involve linux-kernel more. It seems
> the majority of x86-64 users don't even know now this mailing list
> exists, so they don't review or test the latest releases. Also
> the traffic here seems to be less and less now except for me
> (or do I just imagine that?)
>
> I suppose posting all patches there would be too much though, but
> at least the announcements should be going there. I still think
> it's valuable to have some kind of separate x86-64 list because
> linux-kernel is just too much to keep up with and it would
> drown valuable bug reports etc. in the general noise.
>
> Any feedback from x86-64 contributors on how to organize this better
> welcome.
>
> -Andi
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Nigel, Michelle and Alisdair Cunningham
5 Mitchell Street
Cobden 3266
Victoria, Australia
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-06-13 0:34 UTC|newest]
Thread overview: 8+ 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
2006-06-13 0:35 ` Nigel Cunningham [this message]
2006-06-13 8:02 ` Muli Ben-Yehuda
2006-06-17 17:05 ` Andrew Morton
2006-06-18 7:35 ` Andi Kleen
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=200606131035.36012.ncunningham@linuxmail.org \
--to=ncunningham@linuxmail.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