The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] Historic Linux versions not on kernel.org
Date: Sat, 31 Dec 2016 20:32:35 -0800	[thread overview]
Message-ID: <20170101043235.GN5983@mcvoy.com> (raw)
In-Reply-To: <5867e25d.fFUOMfx6x+cso8oD%schily@schily.net>

On Sat, Dec 31, 2016 at 05:52:45PM +0100, Joerg Schilling wrote:
> Warner Losh <imp at bsdimp.com> wrote:
> 
> > I have a ImageMagic CD that I got back in 1994 that I found in my
> > garage. It has a bunch of versions of linux that aren't on kernel.org.
> > The 0.99 series, the 0.98 series and what looks like 1.0 alpha pl14
> > and pl15.
> 
> Isn't everything in the source code controlsystem?
> 
> I thought that everything has been integrated in BitKeeper with help from Larry 
> McVoy. Or are you interested in parts that are not in the kernel?

I didn't help with all that, I was pretty butthurt at the time.  I've
gotten over that but I'm still butthurt that Git won.  It's a really
shitty answer.  I can give you guys a writeup I did recently but I don't
want to spam the list.

I'd be 100% OK with BitKeeper not winning if Git was at parity or better
than BitKeeper, but that's not the case.  It's trivial to do a BK to
Git exporter, it's really hard to do the other direction, Git records
far less information.

It's pretty much what I predicted back in the early 2000's.  If you don't
leave space for commercial companies to make money and pay people to try
and reach for the better answer, you're gonna get mediocre answers.  And
here we are.


      reply	other threads:[~2017-01-01  4:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-30 23:33 Warner Losh
2016-12-31  0:01 ` Wesley Parish
2016-12-31  5:18   ` Robert Swierczek
2016-12-31 11:13 ` Michael Kjörling
2016-12-31 11:30   ` Mantas Mikulėnas
2016-12-31 16:52 ` Joerg Schilling
2017-01-01  4:32   ` Larry McVoy [this message]

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=20170101043235.GN5983@mcvoy.com \
    --to=lm@mcvoy.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;
as well as URLs for NNTP newsgroup(s).