From: Bernd Eckenfels <ecki@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: CVS / Bug Tracking System
Date: Sun, 04 Nov 2001 05:24:37 +0100 [thread overview]
Message-ID: <E160Epp-0008Sa-00@calista.inka.de> (raw)
In-Reply-To: <flk.1004824861.fsf@jens.unfaehig.de>
In article <flk.1004824861.fsf@jens.unfaehig.de> you wrote:
> What are the reasons that Linux isn't kept in an CVS repository?
Some architectures and branches are kept in Source control. Like sparc, xfs.
Also the complete kernel is available in bitkeeper. Linux does not see a
reason to have his version in the CVS. And since he is the only commiter it
is quite valid for him to choose the tool he wants to use.
> mean, it would still give Linus full control over his branch of the
> kernel, and it would make merging of Alan's branches into the main
> branch easier.
It is is not your problem to merge them. Alan and Linus are doing that. And
they are fine without CVS.
BTW: this discussion is very old, you should only start it, if you have new
facts :)
Greetings
Bernd
next prev parent reply other threads:[~2001-11-04 4:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-03 22:01 Jens Müller
2001-11-03 22:21 ` Jeff Garzik
2001-11-04 4:24 ` Bernd Eckenfels [this message]
2001-11-04 5:56 ` Larry McVoy
2001-11-04 23:36 ` Larry McVoy
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=E160Epp-0008Sa-00@calista.inka.de \
--to=ecki@lina.inka.de \
--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
all inboxes | Powered by JetHome®