git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Philip Oakley" <philipoakley@iee.org>
To: "Stefan Beller" <sbeller@google.com>, <git@vger.kernel.org>
Subject: Re: An interesting opinion on DVCS/git
Date: Mon, 9 Mar 2015 14:47:27 -0000	[thread overview]
Message-ID: <4949A08A7B0445C2953FDB0F0C870BF0@PhilipOakley> (raw)
In-Reply-To: CAGZ79kZ8CrjwVh3+OHSV1tv+fRXaDZ_diOO5E7QnSLZ=HTFSfg@mail.gmail.com

From: "Stefan Beller" <sbeller@google.com>
Sent: Monday, March 02, 2015 3:29 AM
> bitquabit.com/post/unorthodocs-abandon-your-dvcs-and-return-to-sanity
> --

The part that the author misses is not all the nice (or not so) stuff 
about having a copy of the full repository locally, for all the reasons 
he mentions, rather it is the *distribution of control*.

In most centralised repo systems there is also centralisation of 
control. The user does not have control. I may initiate a request for 
change, but it's authorisation is always somewhere else, to avoid my 
accidental pollution of the golden source.

The thing that a DVCS brings to the user is an ability to regain a 
little control of their own environment and to include version recording 
within it. The fact that it can be integrated seamlessly into the golden 
source makes it a great tool providing a win-win for all, especially 
when a Hub environment provides a separation between the golden source 
and the user's perambulations and peregrinations that they'd like on a 
safe server.

It is the distribution of Control, not the distribution of Code that 
makes DVCS such a winner (for users). The distribution of all the code 
is icing on the cake (though natural in a FOSS project).
--
Philip 

      parent reply	other threads:[~2015-03-09 14:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54F2CD12.8050609@gmail.com>
2015-03-02  3:29 ` Fwd: An interesting opinion on DVCS/git Stefan Beller
2015-03-03 22:49   ` Shawn Pearce
2015-03-03 23:24     ` Junio C Hamano
2015-03-03 23:55     ` Randall S. Becker
2015-03-04  0:53     ` David Lang
2015-03-04 15:25       ` Michael J Gruber
2015-03-06  3:25         ` Sitaram Chamarty
2015-03-09 14:47   ` Philip Oakley [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4949A08A7B0445C2953FDB0F0C870BF0@PhilipOakley \
    --to=philipoakley@iee.org \
    --cc=git@vger.kernel.org \
    --cc=sbeller@google.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).