9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] SCMs
Date: Tue, 13 Feb 2018 17:47:34 -0800	[thread overview]
Message-ID: <20180214014749.9E42D156E80B@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Tue, 13 Feb 2018 15:13:36 -0800." <alpine.BSF.2.21.1802131453520.23181@orthanc.ca>

On Tue, 13 Feb 2018 15:13:36 -0800 Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
>
> +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.

Git has far too many subcommands and impementation warts but
its underlying model has just 4 types of objects. The
distributed part of git is conceptually fairly simple too.
Over time I have used sccs, rcs, cvs, subversion, mercurial,
git and a couple other SCMs. Each has its pros and cons.  By
now I primarily use git because I can run it on all the
platform and it is quite fast. And there is an active
ecosystem around it. Things like code review systems do help
quite a bit with improving code quality (in my last job I used
gerrit to brainwash people into following good practices by
providing detailed core review comments).

Dave MacFarlane's git client (dgit) does a decent job on plan9.



  parent reply	other threads:[~2018-02-14  1:47 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 [this message]
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

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=20180214014749.9E42D156E80B@mail.bitblocks.com \
    --to=bakul@bitblocks.com \
    --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).