From: Martin Langhoff Date: Tue, 28 Nov 2006 22:47:38 GMT Subject: Re: git and bzr Message-ID: <46a038f90611281447j66ea97f2j9ecbe9af0edcc620@mail.gmail.com> In-Reply-To: <456CB9D3.4060900@onlinehome.de> On 11/29/06, Nicholas Allen wrote: > > ps: hope you don't mind I re-added the CC to git@vger in my reply > > Of course not - I also added bzr mailing list back on this discussion too... Cool > For the kind of development we do this is not really a big deal though > as all developers can agree on using one RCS. But if you mix git and svn > in this way then the changes can only go one way (from svn to git) can't > they as svn is not so intelligent so this somewhat limits its usefulness > doesn't it? Well, if you look in the git toolset, you'll find things like git-svn which is geared to make it almost transparent to use git to work on a project where the upstream is using svn and push patches into SVN (if you have write access, naturally). And git-cvsexportcommit which is a lot less useful but helps me push series of patches from git into cvs easily and with the certaintly that I am not messing up the content. > I know bzr it has some beta level plugin support for SVN foreign > branches (git, mercurial and svk ones too I think) and I believe this > works in both directions. So you can commit to bzr, push that to an svn > repository and also pull changes from svn. Merge branches in bzr and > commit back to svn with log messages and history intact. So bzr still > allows the use of multiple RCS systems... Sounds roughly like git-svn ;-) converge, ye DSCMs