9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Eric Lee Green <eric@badtux.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Publish and be damned.
Date: Fri, 20 Apr 2001 07:13:37 -0700	[thread overview]
Message-ID: <3AE04411.9A7FA44A@badtux.org> (raw)
In-Reply-To: <007201c0c994$81ad3990$e0b6c6d4@SOMA>

Boyd Roberts wrote:
> From: "Lucio De Re" <lucio@proxima.alt.za>
> > I have raised that cry before, but I seem to be just a voice in
> > the wilderness.  However, I can offer a public CVS repository for
> > those who, like me, think that incomplete source is nothing to be
> > ashamed of.
>
> why not just manage a web page with links to the originals
> as a first cut.  then if it works out move on to a more
> complex solution?
>
>     plan to throw one away, you will anyway ...
>
> the web is well established, but CVS?

Huh? CVS is the standard Unix source control system. Most major software
development projects on Unix are managed either using CVS or one of its
commercial competitors. FreeBSD, Apache, etc. all have publically
accessible CVS archives for their developers (CVS has a couple of
different Internet protocols so that unlike, say, Microsoft SourceSafe,
you can use it over the Internet). In fact, you can go to their web site
and browse the CVS archives with your web browser -- click on a file in
the directory tree, and you can see its complete revision history all
the way back to the beginning of time (or 1992, whichever is first :-),
and can click on any of those revisions to see what was that program
looked like at any one of those points in time. CVS also has all the
usual branch management stuff etc., though they are unnecessarily
difficult to use (sigh, at work we have a page on our intranet web site
that tells our engineers nothing except what convulated gibberish CVS
commands to use to create branches, tag releases, and merge changes from
a stable branch into the current development branch).

It puzzles me why you would be opposed to using a standard source
control system to, err, control source? Especially the source control
system that is standard for Internet software (virtually all of the
standard Internet software, such as Apache and Sendmail, are managed via
CVS). Now, I don't know what source control program is used by Bell Labs
internally to manage the Plan 9 sources. If it's a free one, and there's
a web front end to it, that might be the better alternative. I think
Lucio threw out CVS as a possibility because that's what he has, and
would be open to other alternatives -- if anybody offered one, rather
than simply carping that they don't understand standard software
development tools.

There's a right way to do things, and there's an easy way to do things,
and usually the two are completely different ways :-}. The deal is,
though, that in the long term the right way is always easier. As I've
learned to my regret in the past, when 6 months after the project is
released I'm called back to fix it the right way instead of the
quick'n'dirty easy way that I rigged it due to sheer laziness :-}. If
you're going to do a web browser for source code, doing it the right way
(via a web front end into a real source code management system) is,
well, the right way (sigh).

--
Eric Lee Green  http://www.badtux.org  mailto:eric@badtux.org
     Phoenix Branch -- Eric Conspiracy Secret Labs
              Cruisin' the USENET since 1985


  reply	other threads:[~2001-04-20 14:13 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20  5:54 Lucio De Re
2001-04-20 12:22 ` Boyd Roberts
2001-04-20 14:13   ` Eric Lee Green [this message]
2001-04-20 19:15     ` Boyd Roberts
2001-04-20 14:39   ` Lucio De Re
2001-04-20 20:35     ` Christopher Nielsen
2001-04-20 21:02     ` Boyd Roberts
2001-04-21  7:34       ` Lucio De Re
2001-04-21 11:06         ` Boyd Roberts
2001-04-21 12:59           ` Lucio De Re
2001-04-21 13:43             ` Boyd Roberts
2001-04-21 14:20               ` Lucio De Re
2001-04-21 13:08           ` Steve Kilbane
2001-04-22  1:37             ` Boyd Roberts
2001-04-22  9:37               ` Steve Kilbane
2001-04-22 14:51                 ` Boyd Roberts
2001-04-22 15:21                   ` Lucio De Re
2001-04-22 15:42                     ` Boyd Roberts
2001-04-22 15:55                       ` Software Repository
2001-04-22 13:26             ` Lucio De Re
2001-04-22 16:00               ` Dan Cross
2001-04-22 16:13                 ` Lucio De Re
2001-04-22 22:25                   ` Dan Cross
2001-04-22 16:18                 ` Boyd Roberts
2001-04-22 16:33                   ` Lucio De Re
2001-04-22 16:46                     ` Boyd Roberts
2001-04-22 22:14                   ` Dan Cross
2001-04-22 22:16                     ` Boyd Roberts
2001-04-22 22:25                     ` Boyd Roberts
2001-04-22 22:32                     ` Boyd Roberts
2001-04-23 19:31                       ` Dan Cross
2001-04-20 14:52 nemo
2001-04-20 15:11 ` Lucio De Re
2001-04-21 14:34 jmk
2001-04-21 19:03 ` Boyd Roberts
2001-04-22 16:12 rsc
2001-04-22 16:17 ` Lucio De Re
2001-04-22 23:52 rsc
2001-04-23  4:26 ` Lucio De Re
2001-04-23 19:33   ` Dan Cross
2001-04-23 19:32 ` Dan Cross

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=3AE04411.9A7FA44A@badtux.org \
    --to=eric@badtux.org \
    --cc=9fans@cse.psu.edu \
    /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).