From: "M. R. Brown" <mrbrown@0xd6.org>
To: Larry McVoy <lm@work.bitmover.com>,
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: Wed, 17 Apr 2002 14:17:41 -0500 [thread overview]
Message-ID: <20020417191741.GD8530@0xd6.org> (raw)
In-Reply-To: <20020416225752.GA5897@0xd6.org> <20020416160121.B24069@work.bitmover.com> <20020417000818.GB5897@0xd6.org> <20020416181034.C24069@work.bitmover.com> <20020417024149.GC5897@0xd6.org> <20020416203721.B27525@work.bitmover.com> <20020417050412.GD5897@0xd6.org> <20020416230355.I27525@work.bitmover.com> <20020417135215.GA7814@0xd6.org> <20020417105441.Q745@work.bitmover.com>
[-- Attachment #1: Type: text/plain, Size: 1648 bytes --]
* Larry McVoy <lm@bitmover.com> on Wed, Apr 17, 2002:
>
> I think BK can help you and you are so stuck on one way of doing things
> that you are ignoring that possibility. That's OK with me so long as
> it is just you, but you're posting in a public forum, to a group of
> people that I'm trying to help, and as long as you do, I'll be here,
> annoying as heck, explaining why you are wrong. I'm not saying that you
> are wrong about BK drop-ins, you're right about that. We're fixing it as
> fast as we can, it's in my top 3 work items right now. In the meantime,
> if you poked around, there are lots of ways to use BK and I'm 99% sure
> you could find one that would result in less work overall for you than
> what you are doing now. I don't care if *you* find one, I care if
> others find one. We're trying to maximize productive work for the
> largest number of people, and I find your posts counterproductive to
> that goal.
The cool thing is, since the linuxconsole drop-in wasn't going anywhere, I
can move on to more useful pursuits instead of going back and forth with you.
If you want to spend your time denegrating other SCMs and people that don't
subscribe to your divine development tenets, more power to you. I've
learned enough from this thread to not waste time arguing with you. Next
time someone says something about Bitkeeper that I happen to agree or
disagree with, do you suppose I should just e-mail them privately? Or
should I post here to make sure it gets under your scrutinizing eye?
Apologies to those who read this God awful thread without hitting Control-D
first :P.
M. R.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-04-17 19:18 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
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 [this message]
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=20020417191741.GD8530@0xd6.org \
--to=mrbrown@0xd6.org \
--cc=jsimmons@transvirtual.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxconsole-dev@lists.sourceforge.net \
--cc=lm@work.bitmover.com \
/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