9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dan Cross <cross@math.psu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] revision control
Date: Mon, 23 Jan 2006 18:37:20 -0500	[thread overview]
Message-ID: <20060123233720.GP25435@augusta.math.psu.edu> (raw)
In-Reply-To: <43D5644C.8000909@lanl.gov>

uriel@cat-v.org wrote:
> See yesterday(1) and history(1).

As Ron said, that's not really sufficient.  You loose a lot with the
dump filesystem; log messages, branching, granularity, etc.  It's an
answer, but not a universally good one.  But, more to the point, snappy
one-liners like the above just smack of elitism and don't convey any
real information.  Just because it's not the fashionable way to do
something in the Plan 9 world doesn't mean it may not be necessary due
to circumstances beyond an individual's control.  Yeah, I've done enough
elitist bitching in my time, too, but ultimately, did anyone benefit?
Not really.

On Mon, Jan 23, 2006 at 04:18:36PM -0700, Ronald G Minnich wrote:
> CVS is ok.
> 
> The xen guys use mercurial now, which is written in python, and seems to 
> work well. Could this python system be ported to python on plan 9?

I like Subversion; it's a decent tool and has a textual on-disk
representation reminescent of RCS files.  It appears to be, ``CVS done
right.''  Sure, some things are suboptimal, but on the whole, it's
pleasant enough to work with.  But it requires the Apache runtime,
which I guess would be non-trivial to port (because it's big and
requires more patience than I have).

Personally, I'd like to see ports of unison and subversion to Plan 9.
That'd make me a happy guy.  Of course, I'd also like to have a machine
running Plan 9 again.  That'd also make me a happy guy.  Oh yeah, and
time to mess with it, too.  And time to reply to people who try and
help me out of 9fans (hi, Erik!).  Mainly, it's a time thing.

	- Dan C.



  reply	other threads:[~2006-01-23 23:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-23 22:50 Chris Silva
2006-01-23 23:09 ` uriel
2006-01-23 23:18   ` Ronald G Minnich
2006-01-23 23:37     ` Dan Cross [this message]
2006-01-24  0:02       ` Christopher Nielsen
2006-01-24  0:54         ` Charles Forsyth
2006-01-24  3:19           ` Skip Tavakkolian
2006-01-24  2:38             ` Ronald G Minnich
2006-01-24  8:33             ` Steve Simon
2006-01-24 10:24               ` Skip Tavakkolian
2006-01-24 10:53                 ` Charles Forsyth
2006-01-25  7:36           ` Dave Eckhardt
2006-01-25 14:25             ` Wes Kussmaul
2006-01-24  0:04       ` Ronald G Minnich
2006-01-24  1:17         ` Charles Forsyth
2006-01-24  2:06           ` andrey mirtchovski
2006-01-24  2:19         ` uriel
2006-01-24  2:34           ` Ronald G Minnich
     [not found]       ` <000301c6207f$763f4070$14aaa8c0@utelsystems.local>
2006-01-24  8:00         ` "Nils O. Selåsdal"
2006-01-23 23:42     ` Paul Lalonde
2006-01-23 23:55       ` Christopher Nielsen
2006-01-24  1:07     ` uriel
2006-01-26  2:25 FernanBolando
2006-01-26  2:44 ` David Leimbach
2006-01-26 15:53 ` "Nils O. Selåsdal"
2006-01-26 16:27   ` uriel
2006-01-27 23:29     ` andrey mirtchovski

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=20060123233720.GP25435@augusta.math.psu.edu \
    --to=cross@math.psu.edu \
    --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).