The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@bitmover.com (Larry McVoy)
Subject: [TUHS] Re: TUHS Digest, Vol 6, Issue 7
Date: Tue, 11 Nov 2003 19:08:42 -0800	[thread overview]
Message-ID: <20031112030842.GA26882@work.bitmover.com> (raw)
In-Reply-To: <20031112020007.248411FD1@minnie.tuhs.org>

> Date: Tue, 11 Nov 2003 17:39:23 -0800 (PST)
> From: Kenneth Stailey <kstailey at yahoo.com>
> Subject: Re: [TUHS] 32V/I portability
> To: macbiesz at optonline.net, tuhs at minnie.tuhs.org
> Message-ID: <20031112013923.70852.qmail at web60509.mail.yahoo.com>
> Content-Type: text/plain; charset=us-ascii
> 
> 
> --- macbiesz at optonline.net wrote:
> > You could set up a Sourceforge project for 32/I?
> > 
> > Maciek
> 
> Anything but Sourceforge.  You will rue the day you chose them.  Don't take my

If someone gives me a pointer to the tarballs I'll happily import
them into BitKeeper and set up a 32vi.bkbits.net that anyone can use.
Unlike sourceforge, we're about quality, not quantity, but even so,
we have 1/3 as many files under revision control and no performance
problems.  It's not really sourceforge's fault, they choose CVS and CVS
sucks.  As Ted T'so said recently "CVS is not the answer, CVS is the
question.  No is the answer."  :)
-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm


      parent reply	other threads:[~2003-11-12  3:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031112020007.248411FD1@minnie.tuhs.org>
2003-11-12  2:09 ` Larry McVoy
2003-11-12  8:04   ` Wesley Parish
2003-11-12  3:08 ` 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=20031112030842.GA26882@work.bitmover.com \
    --to=lm@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;
as well as URLs for NNTP newsgroup(s).