From: "Martin Brulisauer" <martin@uceb.org>
To: "'Ghozlane Toumi'" <ghoz@sympatico.ca>,
"'George France'" <france@handhelds.org>,
"Oliver Pitzeier" <o.pitzeier@uptime.at>
Cc: linux-kernel@vger.kernel.org
Subject: RE: kbuild 2.5.26 - arch/alpha
Date: Wed, 24 Jul 2002 01:21:12 +0200 [thread overview]
Message-ID: <3D3E0108.1877.32A680F@localhost> (raw)
In-Reply-To: <001a01c2329d$6d588fd0$1211a8c0@pitzeier.priv.at>
On 24 Jul 2002, at 1:05, Oliver Pitzeier wrote:
> > On 23 Jul 2002, at 18:29, George France wrote:
> > > site or mailing list. It is probably better to utilize
> > what exist. Either
> > > the debian-alpha@lists.debian.org, axp-list@redhat.com,
> > > axp-hardware@talisman.alphalinux.org or suse-axp@suse.com. In the
> > > worst
> >
> > As long as these lists are kernel (?) and not user oriented
> > and not too distribution specific.
>
> That's why I think it would be the best to setup a new one. But you'll
> never be able to lock out distribution specify questions and so
> replies... :o(
>
All these mailing lists are used to have kind of a "virtual" team,
are they? If we move the linux/alpha discussions away from
linux-kernel and/or vger.kernel.org how big is the risk that we
solve problems in this list others have already done?
In my oppinion linux/alpha should not be treated as a separate
task, offline from other kernel discussions. Too much information
could get lost - and as we can see now - linux/alpha is way
behind the current tree Linus maintains.
If Linus will participate in a linux/alpha mailing list, then it would
be a good idea - If not ... (guess if he will ;-}).
Regards,
Martin
next parent reply other threads:[~2002-07-23 23:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D3DF93C.16904.30BF311@localhost>
[not found] ` <001a01c2329d$6d588fd0$1211a8c0@pitzeier.priv.at>
2002-07-23 23:21 ` Martin Brulisauer [this message]
[not found] <002b01c23279$84be70a0$1211a8c0@pitzeier.priv.at>
[not found] ` <02072318292300.02533@shadowfax.middleearth>
2002-08-09 10:00 ` kbuild 2.5.26 - arch/alpha Martin Brulisauer
2002-08-09 14:23 ` George France
2002-08-09 17:51 ` Måns Rullgård
2002-08-09 21:03 ` Thunder from the hill
[not found] <20020723202538.NYJJ13064.tomts23-srv.bellnexxia.net@there>
[not found] ` <001701c2329b$a812f6d0$1211a8c0@pitzeier.priv.at>
2002-07-23 23:26 ` Martin Brulisauer
2002-07-21 13:54 Martin Brulisauer
[not found] ` <001101c230d7$c5973c40$1211a8c0@pitzeier.priv.at>
2002-07-23 12:42 ` Martin Brulisauer
2002-07-23 13:28 ` Jan-Benedict Glaw
2002-07-23 23:34 ` Oliver Pitzeier
2002-07-24 6:53 ` Thunder from the hill
2002-07-24 7:07 ` Thunder from the hill
2002-07-24 7:13 ` Martin Brulisauer
2002-07-24 7:45 ` Thunder from the hill
2002-07-23 15:05 ` George France
2002-07-23 16:24 ` Ghozlane Toumi
2002-07-23 17:01 ` Martin Brulisauer
2002-07-23 19:00 ` George France
2002-07-23 19:08 ` Sven Koch
2002-07-23 21:24 ` Jay Estabrook
2002-07-23 20:18 ` Jay Estabrook
2002-07-23 23:44 ` Oliver Pitzeier
2002-07-23 23:35 ` Oliver Pitzeier
2002-07-23 23:54 ` Oliver Pitzeier
2002-07-24 3:51 ` Thunder from the hill
-- strict thread matches above, loose matches on Subject: below --
2002-07-20 8:41 Martin Brulisauer
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=3D3E0108.1877.32A680F@localhost \
--to=martin@uceb.org \
--cc=france@handhelds.org \
--cc=ghoz@sympatico.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=o.pitzeier@uptime.at \
/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