[Kde-scm-interest] svn, git, bzr

Paul Hummer paul.hummer at canonical.com
Mon Jul 21 18:32:47 CEST 2008


Patrick Aljord wrote:
> I've tried mercurial and bazar, they're all good. In the end I prefer
> git because it has more commands to do anything you want though if you
> just want to use the basics you still can, which, in my opinion, is
> very much in the spirit of KDE :D. Plus Git is faster.
>   
Out of curiousity, what commands are you looking for? The thing I love
about bzr is that it's so easy to write a plugin for just about
anything, from generating Changelogs to building deb packages.
>   
>> From what I understood about bzr (I didn't tried it yet !), it seems you can
>> work on a centralized model (as if you were using svn, without merging
>> requests, as you are forced to do on git), and if you get, for instance
>> disconnected (because you traveled somewhere where you have not wifi, or you
>> are during a travel), you can 'unbind', commit freely (decentralized), and
>> then 'bind' again (pushing all commits you did when being 'unbind').
>>
>> I see in bzr's workflow an amazingly dynamic thing, and pretty simple too.
>>
>> So, what do you think ? Have you tried bzr ?
>>     
>
> from the bazar page:
> http://bazaar-vcs.org/Workflows#head-8b6348176ddc592bc64a124bd917e88569615def
>
> "This is essentially the same as the Centralized model, except that
> when developers are making a series of changes, they do "commit
> --local" or unbind their checkout, then commit their work to the
> shared mainline when it is complete."
>
> You can do that with Git too, it's called committing to the same
> repository. In Gitorious for example, just add contributers to your
> repository and you're all committing to the same centralized
> repository and you're all still able to commit locally and branching
> all the way without the need to "unbind".
>
>   
I started using git, then moved to mercurial, and finally landed in
bazaar, all because of it's dynamics. Git and mercurial both imply using
a certain workflow. With many big projects, enforcing a workflow is
detrimental to the project. MySQL has been using MySQL for months now.
Many of the groups inside MySQL use different workflows, and while
bazaar has bent, it hasn't broken. This is a huge testimony to Bazaar's
flexibility in workflow.

Paul


More information about the Kde-scm-interest mailing list