From: Larry McVoy <lm@bitmover.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Larry McVoy <lm@bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 and BitKeeper
Date: Fri, 15 Mar 2002 11:30:01 -0800 [thread overview]
Message-ID: <20020315113001.W29887@work.bitmover.com> (raw)
In-Reply-To: <20020315111022.S29887@work.bitmover.com> <Pine.LNX.4.33.0203151110130.29289-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0203151110130.29289-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Fri, Mar 15, 2002 at 11:20:24AM -0800
On Fri, Mar 15, 2002 at 11:20:24AM -0800, Linus Torvalds wrote:
> The thing is, I think that the "work area" really is overrated.
Tried clearcase?
> There's no reason to have a work area at all if you just had:
> - read-only filesystem for grep/make (autogenerated)
> - separate commands for editing
>
> I don't find it depressing at all to have to use "bk editor" to edit a
> file. I just aliased that one, and I'm all done.
Well, it sort of works. If you use emacs, you're set because emacs can
convert the file from read only to read/write in VC mode, which is something
we'll have to update when we go to the new format.
If you use vim and ctags, it sucks because I haven't yet taught vim how
to go from a read only revision controlled file to a read/write file.
It would be way cool if some vim genius out there showed me how to do
that, I know it is possible, vim has the hooks, I simply don't have the
time to go figure it out.
> But reading the current contents (as opposed to reading some revision) of
> the thing _is_ a perfectly valid thing to do, where the FS interfaces do
> actually map perfectly.
Sure, that part works fine. But the write part is a lot more dicey. And
there has to be some way to get to the revision history for all the tools
that want that.
It's absolutely possible to do all this stuff through the file system
and a collection of smart tools, that's more or less what clearcase is.
But it sucks rocks. One of our biggest selling points is that we *don't*
work like clearcase. ClearCase has shown that it is a performance,
stability, and maintainence nightmare to integrate your SCM with the
filesystem. It means your SCM system is now OS specific. *You* may not
care that we run on AIX/Windows/Whatever, but we have to do that to
survive and make enough money to keep making BK better and it actually
shakes out lots of bugs.
Ask the ClearCase guys if they would choose the BK way or the ClearCase
way, given a second chance, and I'll bet you the smarts would do BK.
> > Whoops, sorry, try it with -Ur, the -U says "user files only, skip the BK crud"
>
> That's better. It doesn't fix the pipe example, though. You're missing the
> -l option to grep etc..
Yeah, point taken. I need a --grep-options=<your favorites here> or something.
I need the same thing for bk diffs.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-03-15 19:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 4:42 Linux 2.4 and BitKeeper Marcelo Tosatti
2002-03-14 6:33 ` Ben Greear
2002-03-14 5:36 ` Marcelo Tosatti
2002-03-14 6:37 ` David S. Miller
2002-03-14 6:42 ` Larry McVoy
2002-03-14 7:54 ` Alex Riesen
2002-03-14 15:46 ` Larry McVoy
2002-03-14 18:10 ` Alex Riesen
2002-03-14 18:19 ` Ben Greear
2002-03-14 18:26 ` Robert Love
2002-03-14 18:40 ` Ben Greear
2002-03-14 22:56 ` Mark Frazer
2002-03-15 11:10 ` David Woodhouse
2002-03-15 16:04 ` Larry McVoy
2002-03-15 16:17 ` Stelian Pop
2002-03-15 17:58 ` Linus Torvalds
2002-03-15 18:16 ` Jeff Garzik
2002-03-15 18:27 ` Linus Torvalds
2002-03-15 18:47 ` Larry McVoy
2002-03-17 0:39 ` Daniel Phillips
2002-03-17 5:42 ` Mike Fedyk
2002-03-18 16:47 ` [PATCH] 2.5.7-pre2 IDE 22a Martin Dalecki
2002-03-15 18:39 ` Linux 2.4 and BitKeeper Larry McVoy
2002-03-15 19:01 ` Linus Torvalds
2002-03-15 19:10 ` Larry McVoy
2002-03-15 19:20 ` Linus Torvalds
2002-03-15 19:30 ` Larry McVoy [this message]
2002-03-16 0:31 ` Andreas Ferber
2002-03-16 1:02 ` Andreas Dilger
2002-03-15 16:10 ` David Woodhouse
2002-03-15 4:35 ` Stephen Torri
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=20020315113001.W29887@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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