9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steve Simon <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] SCMs
Date: Wed, 14 Feb 2018 09:01:58 +0000	[thread overview]
Message-ID: <2A1056C9-BD0F-476B-9E30-E47CC5098D17@quintile.net> (raw)
In-Reply-To: <alpine.BSF.2.21.1802131453520.23181@orthanc.ca>

fyi

i spoke too soon, the labs website went a while ago, but the sources machine has returned, well i was able to access it last week.

last chance (i suspect) for those wanting to download the contrib dirs before they disappear - i got mine 😀

-Steve
 

On 13 Feb 2018, at 23:13, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:

>>> I struggle to understand how version control is not more actively used.
> 
>> It's not particularly necessary when you have global state with
>> snapshots provided by a shared WORM fs.
> 
> I always thought that argument was a bit suspect.  And with the loss of sources.bell-labs.com, it's apparent why.  The only revision history was in the venti.  Now that that is lost, so is that history.  I know that there are partial mirrors of sources, but none go all the way back to the dawn of the sources venti archive.  And on the mirrors, we lose the 'blame' functionality fossil provided by tracking who last updated a file.
> 
> If this had been hosted in an SCM, it would have been so simple to replicate that full history elsewhere.
> 
> The other bit that snapshots/dumps miss is context.  When everyone working on the code was within shouting distance of the "unix room" that wasn't an issue.  But now, that context has been lost.  Annotations about the "why" of a commit are as important as the "what."  diffy(1) answers the "what," but not the "why."
> 
>> DVCS adds a lot of complexity
>> for questionable gain, in that environment.  9front's adoption of
>> mercurial is a historical accident rather than a desired outcome.  But,
>> I understand that most people just want to use the tools they already
>> know.  It's much easier than learning a new paradigm.
> 
> +100 on DVCS and needless complexity.  cvs or sccs provides all the functionality I've ever needed in an SCM system.  Although I confess I have been seduced by git's ability to instantly create and switch between branches.  It makes trying out "what if" scenarios completely painless. But it's not enough to convince me to use git except on very rare occasions.
> 
> --lyndon
> 




      parent reply	other threads:[~2018-02-14  9:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13 23:13 Lyndon Nerenberg
2018-02-14  1:03 ` Erik Quanstrom
2018-02-14  1:47 ` Bakul Shah
2018-02-14  7:20   ` Rui Carmo
     [not found]     ` <CAG2UyHq3mVuBRfoHMte0e6z-d5rLrsYqYz9UyNe6_t0Mgxm5hg@mail.gmail.com>
     [not found]       ` <CAG2UyHpKNrT6YWfJ3xg3ijrSmJS57Xao+DcMggaQcL49acwMUQ@mail.gmail.com>
     [not found]         ` <CAG2UyHp727zcSFBsQKRnqSJaFzmxjfaBe_9GwYTgsfv-xFTb2g@mail.gmail.com>
     [not found]           ` <CAG2UyHpUAmd5PyvMT+jDJkmkvUy+ZxO39bc6eBCCC2Jx9JT92g@mail.gmail.com>
     [not found]             ` <CAG2UyHrbgi0nuP3jkGjNkV8AYtugY1u8vaZO5ZKg_kf8SbQddg@mail.gmail.com>
2018-02-14 12:39               ` Dave MacFarlane
2018-02-14 16:30                 ` Lucio De Re
2018-02-14  9:01 ` Steve Simon [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=2A1056C9-BD0F-476B-9E30-E47CC5098D17@quintile.net \
    --to=steve@quintile.net \
    --cc=9fans@9fans.net \
    /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).