[Info-vax] Where to locate software
Craig A. Berry
craigberry at nospam.mac.com
Thu Jun 16 18:48:36 EDT 2016
On 6/16/16 2:32 PM, Richard Levitte wrote:
> Den torsdag 16 juni 2016 kl. 18:12:24 UTC+2 skrev Craig A. Berry:
>> Yes, and a centralized VCS forces you to work that way, while a DVCS
>> frees you from that by disaggregating commit and push.
> Actually, I'd say that what has really enabled this is the superior
> branching (and merging) capability of modern DCVSs.
>
> This view comes from the way we work on OpenSSL, where we do
> constantpeer review, so we constantly create new branches, be it for an easy fix
> or for a complex change, and push them to our internal repo, where
> others in the team can have a look, comment, come with ideas or
> alternative implementations, yada yada yada.
>
> Still, however, your point has its value, that the separation of
> commit and push does enable you to reassess, reorganize and clean up the
> changesets before pushing (as well as after, as comments from my peers
> come in). I just don't think that this point alone is the whole thing
> that validates the freedom you're talking about.
I agree that easy branching and merging are important too (I was trying
to explain the simplest, most tangible difference to someone insisting
there was no difference). I perhaps should have also noted that branches
as well as individual commits can be local until you're ready to push.
As you rightly point out, this in no way hinders collaboration; it just
means you collaborate when you choose to. Plus there are other features
that make collaboration easier, such as the ability to have multiple
remotes. I suspect you use that latter feature if the "internal repo"
you mention is different from the public one at https://git.openssl.org.
More information about the Info-vax
mailing list