From: Josef Roehrl <josefr@emspace.com>
To: Christian Daudt <csd_ob@daudt.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux-kernel-revision-control list (was: Re: Never ever use word BitKeeper if Larry does not like you)
Date: Sat, 15 Mar 2003 23:56:52 -0800 [thread overview]
Message-ID: <3E742E44.7080106@emspace.com> (raw)
In-Reply-To: 200303140856.11839.csd_ob@daudt.org
I second that emotion. Let's not lose track, though, of how the
BitKeeper issue affects kernel development. Giving the BitKeeper
discussions their own home
achieves 2 things: keeps the kernel development list focused on kernel
development and gets the BitKeeper issues hashed out better by making
those its own separate forum.
Regards,
Josef
Christian Daudt wrote:
>This BitKeeper subject resurfaces every week or so and probably accounts for
>5-10% of the linux-kernel mailing list traffic. While a terribly interesting
>topic to some - it really isn't about the kernel. Could someone be so kind as
>to create a linux-kernel-bitkeeper (or linux-kernel-revision-control) mailing
>list so that these discussions (which obviously are not going away) can have
>a proper home?
>
> cheers,
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-03-16 7:37 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 10:51 Never ever use word BitKeeper if Larry does not like you Pavel Machek
2003-03-14 11:19 ` Murray J. Root
2003-03-14 11:50 ` Lars Marowsky-Bree
2003-03-14 13:35 ` Richard B. Johnson
2003-03-14 14:43 ` Larry McVoy
2003-03-14 16:10 ` Alan Cox
2003-03-14 15:14 ` Larry McVoy
2003-03-14 16:11 ` Stephen C. Tweedie
2003-03-14 16:21 ` John Jasen
2003-03-14 16:28 ` Stephen C. Tweedie
2003-03-14 16:37 ` Larry McVoy
2003-03-14 16:56 ` Linux-kernel-revision-control list (was: Re: Never ever use word BitKeeper if Larry does not like you) Christian Daudt
2003-03-15 2:29 ` Joshua Kwan
2003-03-16 7:56 ` Josef Roehrl [this message]
2003-03-14 17:09 ` Never ever use word BitKeeper if Larry does not like you Davide Libenzi
2003-03-14 18:29 ` Jeff Garzik
2003-03-14 18:48 ` Davide Libenzi
2003-03-14 17:10 ` Stephen C. Tweedie
2003-03-14 21:12 ` Mike Galbraith
2003-03-15 0:59 ` Stephen Satchell
2003-03-14 18:57 ` Wichert Akkerman
2003-03-14 20:49 ` Roger Luethi
2003-03-14 21:55 ` Eric Sandall
2003-03-15 0:56 ` Stephen Satchell
2003-03-15 3:36 ` Werner Almesberger
2003-03-15 12:20 ` Pavel Machek
2003-03-16 0:57 ` Alan Cox
2003-03-16 5:01 ` Oliver Xymoron
2003-03-14 16:29 ` Alan Cox
2003-03-14 15:29 ` Larry McVoy
2003-03-14 16:43 ` Alan Cox
2003-03-14 16:43 ` Tom Sightler
2003-03-14 16:58 ` Larry McVoy
2003-03-14 17:56 ` Tom Sightler
2003-03-14 18:34 ` Valdis.Kletnieks
2003-03-14 17:44 ` Pavel Machek
2003-03-14 20:37 ` Teodor Iacob
2003-03-14 18:29 ` Brian McGroarty
2003-03-14 20:33 ` Teodor Iacob
2003-03-14 21:32 ` Brian McGroarty
2003-03-14 12:06 ` Matthias Andree
2003-03-14 15:38 ` Alan Cox
2003-03-14 16:00 ` Mark Mielke
2003-03-14 16:03 ` Larry McVoy
2003-03-14 16:30 ` Mark Mielke
2003-03-14 23:13 ` Daniel Phillips
2003-03-14 13:42 ` Tomas Szepe
2003-03-14 14:33 ` Never ever send Pavel private mail unless you want him to publish it Vlad@geekizoid.com
2003-03-14 14:50 ` Valdis.Kletnieks
2003-03-14 16:13 ` Mark Mielke
2003-03-17 0:16 ` Stuart MacDonald
2003-03-17 0:44 ` Tim Smith
2003-03-17 8:43 ` Helge Hafting
2003-03-17 0:57 ` Vlad@geekizoid.com
2003-03-17 2:16 ` Stuart MacDonald
2003-03-17 2:16 ` David Lang
2003-03-17 4:37 ` Vlad@geekizoid.com
2003-03-17 6:21 ` Oliver Xymoron
2003-03-17 14:56 ` Vlad@geekizoid.com
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=3E742E44.7080106@emspace.com \
--to=josefr@emspace.com \
--cc=csd_ob@daudt.org \
--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