From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: szepe@pinerecords.com, colin@gibbs.dhs.org,
linux-kernel@vger.kernel.org, tcallawa@redhat.com,
sparclinux@vger.kernel.org, aurora-sparc-devel@linuxpower.org
Subject: Re: 2.4 SRMMU bug revisited
Date: 28 May 2002 12:58:38 +0100 [thread overview]
Message-ID: <1022587118.4124.49.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20020527.204114.126236775.davem@redhat.com>
On Tue, 2002-05-28 at 04:41, David S. Miller wrote:
> From: Tomas Szepe <szepe@pinerecords.com>
> Date: Mon, 27 May 2002 23:30:16 +0200
>
> http://linux.bkbits.net:8080/linux-2.4/
>
> The BK repository to use has the URL:
>
> bk://linux.bkbits.net/linux-2.4
>
> The web stuff is updated still by hand and is as a result chronically
> out of date.
Which is a concern since both Linus and Larry made it clear bitkeeper
would *NEVER* be required of contributors. Is there nothing generating
nightly tarballs off cron right now ?
next prev parent reply other threads:[~2002-05-28 10:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 9:24 Tomas Szepe
2002-05-27 10:17 ` David S. Miller
2002-05-27 6:20 ` Tomas Szepe
2002-05-27 10:40 ` David S. Miller
2002-05-27 11:19 ` [aurora-sparc-devel] " Tomas Szepe
2002-05-28 16:41 ` Denis Vlasenko
2002-05-28 12:11 ` David S. Miller
2002-05-27 18:46 ` Colin Gibbs
2002-05-27 19:34 ` Colin Gibbs
2002-05-28 1:12 ` Tomas Szepe
2002-05-27 21:30 ` Tomas Szepe
2002-05-28 3:41 ` David S. Miller
2002-05-28 5:40 ` Tomas Szepe
2002-05-28 8:39 ` David Woodhouse
2002-05-28 11:58 ` Alan Cox [this message]
2002-05-28 11:05 ` David S. Miller
2002-05-28 12:10 ` Ben Collins
2002-05-28 12:19 ` David S. Miller
2002-05-28 0:40 ` David S. Miller
2002-05-29 21:42 ` Tomas Szepe
[not found] <mailman.1022584088.5530.linux-kernel2news@redhat.com>
2002-05-28 16:12 ` 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=1022587118.4124.49.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=aurora-sparc-devel@linuxpower.org \
--cc=colin@gibbs.dhs.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=szepe@pinerecords.com \
--cc=tcallawa@redhat.com \
/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®