On 2008-05-16 11:01:52 +0100, Sak Wathanasin <sw@[EMAIL PROTECTED]
> said:
> On 16 May, 09:33, John Swinbank <swinb...@[EMAIL PROTECTED]
> wrote:
>> In article
>> <a12c83da-d5ea-4fc3-ad4c-332167210...@[EMAIL PROTECTED]
>,
>> Sak Wathanasin <s...@[EMAIL PROTECTED]
> wrote:
>>
>>> What's so special about git?
>>
>> For me, the im****tant features are disconnected operation and (oddly
>> enough) svn sup****t.
>>
>> We have a group svn server. I use git to sync to it on my laptop, then
I
>> can head off to somewhere with no internet access -- park, cafe,
>> whatever -- and commit/revert/branch/merge/etc to my heart's content.
>> Then, when I'm back at my desk, a simple "git svn dcommit" will merge
>> all my changes back to the svn server.
>
> Neat, but how often would I want to be doing repository maintenance
> offline? It might be useful for moving the repository from one server
> to another (of different architectures or versions of BDB), I guess.
John wasn't saying you'd be doing repository *maintenance* offline.
You'd be committing stuff while offline, doing everything you'd
normally do while online.
The main (and confusing) thing about git and mercurial et al is that
there are lots of repositories, and the tools don't enforce any policy
about which one is "it". (Whatever "it" means.) But this lets you work
on an offline repository and then sync things up afterwards with other
repositories, and it allows other modes of working as well.
> Probably worth a look though.
Quite a number of open source projects are moving from svn to mercurial
and git.
Cheers,
Chris
|
