The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] Claim your early Unix contributions on GitHub
Date: Wed, 30 Mar 2016 20:40:03 -0700	[thread overview]
Message-ID: <20160331034003.GB2940@mcvoy.com> (raw)
In-Reply-To: <1459395248.1744911.564290610.78552513@webmail.messagingengine.com>

On Wed, Mar 30, 2016 at 11:34:08PM -0400, Random832 wrote:
> On Wed, Mar 30, 2016, at 23:20, Larry McVoy wrote:
> > On Wed, Mar 30, 2016 at 05:07:29PM -0400, Random832 wrote:
> > > On Wed, Mar 30, 2016, at 15:17, Larry McVoy wrote:
> > > > You are the first person outside of BitMover that I've ever seen
> > > > recognize that.  Go you!  It's very annoying, we can write a perfect BK
> > > > to Git exporter but going the other way is a research project.
> > > 
> > > Didn't you sue someone for writing a BK to Git exporter?
> > 
> > Nope.  In 18 years of business we've never sued anyone.
> 
> Sorry, I guess I got the timeline and the specifics mixed up (the stuff
> about a non-compete agreement - I've never heard of any other company
> having such a thing for their _customers_ - made me assume that there
> was an attempt to actually enforce that), but it certainly seemed like
> you were not very big fans of the idea of a perfect BK-to-_anything_
> exporter, since then you'd lose control of the users whose metadata you
> had locked up in your servers.

Dear Mr or Ms Random832, 

The BK flame wars are long gone, Git won.  Not really interested in 
rehashing all of that.  Especially not here.  Please take your ax
and grind it elsewhere if that is what you want to do.

To the rest of the list, sorry about this, not my intent to have these
"discussions" here.

--lm


  reply	other threads:[~2016-03-31  3:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30  7:53 Diomidis Spinellis
2016-03-30 12:31 ` Joerg Schilling
2016-03-30 13:10   ` Diomidis Spinellis
2016-03-30 13:44     ` Joerg Schilling
2016-03-30 19:17   ` Larry McVoy
2016-03-30 21:07     ` Random832
2016-03-30 23:03       ` Joerg Schilling
2016-03-31  3:20       ` Larry McVoy
2016-03-31  3:34         ` Random832
2016-03-31  3:40           ` Larry McVoy [this message]
2016-03-30 23:42     ` Joerg Schilling
2016-03-31  3:54       ` Larry McVoy
2016-03-30 14:25 ` Marc Rochkind
2016-03-30 15:23   ` Joerg Schilling
2016-03-30 19:14     ` Larry McVoy
2016-03-30 15:49   ` Diomidis Spinellis
2016-03-30 16:07     ` Joerg Schilling
2016-03-30 16:29       ` Diomidis Spinellis
2016-03-30 16:14     ` Pat Barron
2016-03-31 21:06       ` Clem Cole
2016-03-31 21:54         ` Ron Natalie
2016-04-01  9:01         ` Diomidis Spinellis
2016-04-01 14:41           ` Clem Cole
2016-04-01 21:00           ` Jeremy C. Reed
2016-04-01 13:06         ` Dave Horsfall
2016-04-01 21:52         ` Pat Barron
2016-03-30 16:30     ` Marc Rochkind
2016-03-30 16:40       ` Joerg Schilling
2016-03-30 16:55       ` John Cowan
2016-03-30 18:28 Norman Wilson
2016-03-30 20:06 ` Ronald Natalie

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=20160331034003.GB2940@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).