From: Pete Zaitcev <zaitcev@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4 SRMMU bug revisited
Date: Tue, 28 May 2002 12:12:53 -0400 [thread overview]
Message-ID: <200205281612.g4SGCr821003@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1022584088.5530.linux-kernel2news@redhat.com>
>> 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 ?
It is still not required, in theory. A developer may elect
to wait until the change recycles all the way to Linus,
then receive it with regular kernels. This is what I do --
tired of BK... Also, I am too stupid to understand the
concept of changeset.
-- Pete
next parent reply other threads:[~2002-05-28 16:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1022584088.5530.linux-kernel2news@redhat.com>
2002-05-28 16:12 ` Pete Zaitcev [this message]
2002-05-27 9:24 2.4 SRMMU bug revisited 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 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
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
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=200205281612.g4SGCr821003@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--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