Sonia Hamilton <[email protected]> writes:
> * Robert Collins <[email protected]> [2009-03-19 12:02:41 +1100]:
>
>> On Thu, 2009-03-19 at 11:46 +1100, Sonia Hamilton wrote:
>> > Is there any reason why you want to use a *distributed* VCS? For
>> > personal stuff it's probably overkill, and using a centralised VCS will
>> > make your life easier. In which case use Subversion.
>>
>> Whoa there Tonto. Using *nearly* any DVCS is simpler for personal use
>> than using a centralised client-server system like svn.
>
> Why?
>
> I'm still learning git, but one of the things I found annoying was
> that I need to commit to the local repo, then merge my changes up my
> "central" git repo, then commit my changes on the "central" git repo.
That implies that you have changes in the central repository that you
need to merge...
> (Maybe I'm doing it the wrong way, I'm only up to "page 2" of the
> manual). Whereas with a centralised VCS check in only takes one step.
...while this doesn't. At least, there are the two of the same three
steps with Subversion in the case of changes in the upstream repository:
1. Try to commit (or already know that you need to merge.)
2. Merge changes from the central repository.
3. Commit your merged changes to the central repository.
In the trivial case git, like most DVCS tools, is a two step process:
1. Local commit (repeat as desired)
2. push to central repository.
Anyway, in the general case ...
> However I can see the advantages mentioned by John Ferlito of better
> branching in DVCS's.
The key advantage that attracts me is any ^W better merging support from
the tool; without that life is, as they quote goes, pain.
With git that means that I can interact with changes in the upstream
repository[1] without having to think very hard: git handles merging
them during the commit process without drama, very much unlike
Subversion did.
> And of course if you've regularly got limited connectivity, a DVCS is
> the only way to go.
*nod* I also find that if you need to make changes in two or more
locations a DVCS usually saves both time and trouble, through merging
and/or easier replication of changes.
Regards,
Daniel
Footnotes:
[1] Typically Subversion, since my employer uses that for their VCS,
and I find the benefits of 'git svn' substantially outweigh the
costs of using a different tool.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
