From: Andi Kleen <ak@suse.de>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Petition Against Official Endorsement of BitKeeper by Linux Maintainers
Date: 06 Mar 2002 10:40:44 +0100 [thread overview]
Message-ID: <p73vgca11b7.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <20020305165233.A28212@fireball.zosima.org.suse.lists.linux.kernel> <3C8543CC.A6017F76@zip.com.au.suse.lists.linux.kernel>
In-Reply-To: Andrew Morton's message of "5 Mar 2002 23:21:01 +0100"
Andrew Morton <akpm@zip.com.au> writes:
> The Open Source Club at The Ohio State University wrote:
> >
> > [ succinctness ]
> >
>
> fwiw, I prefer to not use bitkeeper, for the reasons which
> you outline.
I also prefer not to use Bitkeeper as long as possible for similar reasons
and because it is too slow and clumpsy
(although it is already very hard because often source is only available
through it, e.g. for ppc or for 2.5 pre patches now -- hopefully this trend
does not continue)
-Andi
next parent reply other threads:[~2002-03-06 9:41 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020305165233.A28212@fireball.zosima.org.suse.lists.linux.kernel>
[not found] ` <3C8543CC.A6017F76@zip.com.au.suse.lists.linux.kernel>
2002-03-06 9:40 ` Andi Kleen [this message]
2002-03-06 10:17 ` Petition Against Official Endorsement of BitKeeper by Linux Maintainers Dave Jones
2002-03-06 14:48 ` Paul P Komkoff Jr
2002-03-06 15:59 ` yodaiken
2002-03-06 13:26 ` Geert Uytterhoeven
2002-03-06 14:30 ` Roman Zippel
2002-03-06 17:00 ` Larry McVoy
2002-03-06 18:11 ` Roman Zippel
2002-03-07 4:27 ` Troy Benjegerdes
2002-03-07 16:51 ` Henning P. Schmiedehausen
2002-03-07 17:26 ` Mark Mielke
2002-03-07 17:39 ` Rik van Riel
2002-03-08 10:07 ` Matthias Andree
2002-03-08 18:05 ` [lkml] " Ian Soboroff
2002-03-07 18:10 Nicholas Berry
-- strict thread matches above, loose matches on Subject: below --
2002-03-07 18:02 Jean-Luc Leger
2002-03-07 18:33 ` Cort Dougan
2002-03-05 22:33 rddunlap
2002-03-05 21:52 The Open Source Club at The Ohio State University
2002-03-05 22:16 ` Andrew Morton
2002-03-05 22:38 ` Troy Benjegerdes
2002-03-06 0:51 ` Larry McVoy
2002-03-06 14:54 ` Kent Borg
2002-03-06 16:56 ` Larry McVoy
2002-03-06 22:13 ` Pavel Machek
2002-03-07 16:17 ` Troy Benjegerdes
2002-03-07 19:54 ` Andrew Morton
2002-03-07 20:15 ` Larry McVoy
2002-03-07 20:38 ` yodaiken
2002-03-07 20:50 ` Troy Benjegerdes
2002-03-07 20:53 ` Larry McVoy
2002-03-07 21:23 ` Andrew Morton
2002-03-07 21:42 ` Rik van Riel
2002-03-07 21:47 ` Anton Altaparmakov
2002-03-07 20:50 ` Cort Dougan
2002-03-07 21:12 ` Rik van Riel
2002-03-07 21:15 ` Cort Dougan
2002-03-07 21:47 ` Andrew Morton
2002-03-07 21:58 ` Cort Dougan
2002-03-07 21:58 ` Rik van Riel
2002-03-07 22:08 ` Jeff Garzik
2002-03-07 22:46 ` Florian Weimer
2002-03-07 22:42 ` Florian Weimer
2002-03-07 19:18 ` Linus Torvalds
2002-03-07 19:32 ` Larry McVoy
2002-03-07 20:12 ` george anzinger
2002-03-05 22:41 ` Jeff V. Merkey
2002-03-05 22:50 ` Kilobug
2002-03-05 23:29 ` Stephen Samuel
[not found] ` <004301c1c4a6$ab218340$b0d3fea9@pcs686>
2002-03-08 1:39 ` Stephen Samuel
2002-03-08 2:25 ` Alexander Viro
2002-03-08 3:32 ` yodaiken
2002-03-08 4:35 ` Andreas Dilger
2002-03-08 7:56 ` Sean Hunter
2002-03-06 2:23 ` Karl
2002-03-06 3:47 ` Jeff V. Merkey
2002-03-05 23:58 ` Alan Cox
2002-03-06 7:50 ` Eric W. Biederman
2002-03-06 15:58 ` Rik van Riel
2002-03-07 9:15 ` Pau Aliagas
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=p73vgca11b7.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=akpm@zip.com.au \
--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