Bzr is dying; Emacs needs to move
lists.gnu.org
Bzr is dying; Emacs needs to move
1–10 of 317 posts
Re: Bzr is dying; Emacs needs to move
#2Re: Bzr is dying; Emacs needs to move
#3Re: Bzr is dying; Emacs needs to move
#4For those wondering: Vim is currently on Mercurial @ Google Code [1] [1] http://www.vim.org/sources.php
https://github.com/cosmin/git-hg
Submitting patches upstream is also not a problem as Bram Moolenaar only accepts patch files on the dev mailing list.
Re: Bzr is dying; Emacs needs to move
#5git init ; bzr fast-export --plain | git fast-import
Re: Bzr is dying; Emacs needs to move
#6the most annoying thing about bzr in my opinion is it's stupid branching model. luckily a migration to git is a oneliner. git init ; bzr fast-export --plain | git fast-import
I wish. Unfortunately, not all repos we use are owned by us, and using two VCSs is worse than sticking with bzr.
Re: Bzr is dying; Emacs needs to move
#7Sad, but true...
Re: Bzr is dying; Emacs needs to move
#8Re: Bzr is dying; Emacs needs to move
#9Oddly, both Bazaar, Git and Mercurial were created around March/April 2005. Why the sudden appearance of popular DVCSs around that time, and why did Bazaar fall behind the other two in popularity?
github also contributed to amplify the adoption as its makes it really easy to use (even thus people generally use git in a non-distributed way with github)
(i do prefer git in usage, tho, but thats subjective i suppose)
Re: Bzr is dying; Emacs needs to move
#10Oddly, both Bazaar, Git and Mercurial were created around March/April 2005. Why the sudden appearance of popular DVCSs around that time, and why did Bazaar fall behind the other two in popularity?