From: Larry McVoy <lm@bitmover.com>
To: "M. R. Brown" <mrbrown@0xd6.org>
Cc: James Simmons <jsimmons@transvirtual.com>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux console project <linuxconsole-dev@lists.sourceforge.net>
Subject: Re: [Linux-fbdev-devel] Fbdev Bitkeeper repository
Date: Tue, 16 Apr 2002 16:01:21 -0700 [thread overview]
Message-ID: <20020416160121.B24069@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10204161542470.29030-100000@www.transvirtual.com> <20020416225752.GA5897@0xd6.org>
> Please tell us that primary framebuffer/input/console development will
> continue in the CVS drop-in tree on SourceForge? Bitkeeper is unable to
> support this (easier, more efficient) style of development.
Could you please explain why you think CVS is easier and more efficient?
Last I checked, BK was a superset of CVS, but could be used pretty much
identically to CVS if that's what you want.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-04-16 23:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 22:46 Fbdev Bitkeeper repository James Simmons
2002-04-16 22:57 ` [Linux-fbdev-devel] " M. R. Brown
2002-04-16 23:01 ` Larry McVoy [this message]
2002-04-17 0:08 ` M. R. Brown
2002-04-17 1:10 ` Larry McVoy
2002-04-17 2:41 ` M. R. Brown
2002-04-17 3:37 ` Larry McVoy
2002-04-17 5:04 ` M. R. Brown
2002-04-17 6:03 ` Larry McVoy
2002-04-17 12:32 ` Roman Zippel
2002-04-17 13:52 ` M. R. Brown
2002-04-17 17:21 ` James Simmons
2002-04-17 17:54 ` Larry McVoy
2002-04-17 19:17 ` M. R. Brown
2002-04-17 16:47 ` Jan Harkes
2002-04-17 17:05 ` 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=20020416160121.B24069@work.bitmover.com \
--to=lm@bitmover.com \
--cc=jsimmons@transvirtual.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxconsole-dev@lists.sourceforge.net \
--cc=mrbrown@0xd6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.