From: Mike Fedyk <mfedyk@matchmail.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Larry McVoy <lm@bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 and BitKeeper
Date: Sat, 16 Mar 2002 21:42:17 -0800 [thread overview]
Message-ID: <20020317054217.GA27249@matchmail.com> (raw)
In-Reply-To: <3C90E994.2030702@candelatech.com> <a6teec$sis$1@penguin.transmeta.com> <20020315104705.N29887@work.bitmover.com> <E16mOiH-0000mh-00@starship>
In-Reply-To: <E16mOiH-0000mh-00@starship>
On Sun, Mar 17, 2002 at 01:39:52AM +0100, Daniel Phillips wrote:
> On March 15, 2002 07:47 pm, Larry McVoy wrote:
> > Here's the deal. I know you guys all think that I'm a genius and
> > everything, but I'm actually dumb as a board. The "design mistake"
> > was made so that I could have BK generate pure SCCS files and test that
> > I did the same thing as a known working tool, ATT SCCS. By doing that,
> > I easily saved myself a year of design. Making interleaved deltas work
> > is hard for me (we have Rick here now and he's forgotten more about this
> > stuff than I'll ever know, but we didn't have him when I wrote the SCCS
> > compat weave).
> >
> > [...]
> >
> > I'm gonna hack at least make & patch to know about the new format and
> > work the way they do now. So I can have your cake and eat it too.
> > If I can't get the FSF to take the changes, we'll just ship 'em,
> > we ship diff & patch already, so it's not so hard to alias make='bk make'.
>
> While you're in there, is there any way I can have an option to have the
> 'shouting' SCCS become .SCCS or something, so a normal listing just shows
> the files I'm interested in?
>
It seems like once all of the bk information is kept in one file per
repository that the one file can be named something like .bk.db or something
like that and thus fix the problem you're having...
next prev parent reply other threads:[~2002-03-17 5:41 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 [this message]
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
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=20020317054217.GA27249@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=phillips@bonn-fries.net \
/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