[Info-vax] Where to locate software

[Craig A. Berry]

On 6/15/16 12:41 PM, Johnny Billquist wrote:
> On 2016-06-15 17:03, Craig A. Berry wrote:
>> On Wednesday, June 15, 2016 at 8:23:40 AM UTC-5, Johnny Billquist wrote:
>>> On 2016-06-15 14:39, Craig A. Berry wrote:
>>>> On 6/15/16 4:18 AM, Johnny Billquist wrote:

>>> (The way you do this is that you create a branch where you do all your
>>> experimentation, and then you merge back to the source when you want
>>> others to see it. And yes, you can have several people working on your
>>> experimental branch in parallel as well. And they can all check in and
>>> out things concurrently. This is what branches exist for.)
>>
>> It's not the same thing.  The branches (even nominally "private" ones)
>> exist on the server in a centralized VCS.  Plus there is no
>> distinction between commit and push; if you create a changeset, you
>> are creating it on the server.  (Unless you have a completely private
>> repository, I guess.)
>
> But now you are talking about technical implementation details. The
> usage pattern is the same. It's not that git enables me to do something
> I couldn't already do, it just have different names, and different
> technical solutions to how it might be done.

If needing to communicate with the server is the same thing as not
needing to communicate with the server, and being unable to commit
without publishing is the same thing as being able to commit without
publishing, and being unable to create a changeset without contending
with other users' changes is the same thing as being able to do so, then
yeah, it's all the same. In other words, if you don't understand or
refuse to use the features of a DVCS, then it's the same as a
centralized VCS.

> But I will not be doing my work in any different way.

That I believe.