All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [RFC] Moving from Bazaar (bzr) to git
Date: Sat, 22 Jun 2013 23:40:31 +0400	[thread overview]
Message-ID: <20130622234031.2f886a3d@opensuse.site> (raw)
In-Reply-To: <CAMPnHXwgP04HCoJvRJzyoUiN57hGH2kigvu+WRu6hjsfJOP0AA@mail.gmail.com>

В Sun, 23 Jun 2013 00:09:31 +0530
Keshav Padram <the.ridikulus.rat@gmail.com> пишет:

> On 22 June 2013 23:30, Paul Menzel <paulepanter@users.sourceforge.net>wrote:
> 
> > Dear GRUB folks,
> >
> >
> > this is *not* the start of a flame war about what VCS is the best.
> >
> > Hopefully everyone will agree, that git is the most popular one in the
> > FOSS world (Linux, freedesktop.org, GNOME, KDE, …) and a lot of people
> > are now familiar with the basic git commands. So using Bazaar is one
> > more thing to deal with for new contributors before making a
> > contribution to GRUB. (I know there is git-bzr-ng, but it is still one
> > more step.)
> >
> > Talking to Vladimir and Colin in #grub, they did not oppose a migration
> > to git and Vladimir asked me to bring it up on the list.
> >
> > Does anyone have experience with such a move and how to do it on
> > Savannah? Could you please share these? That would be great.
> >
> >
> I don't have an idea how to do it in Savannah. But you can also use
> git-remote-bzr (
> http://felipec.wordpress.com/2012/11/13/git-remote-hg-bzr-2/ ) apart from
> git-bzr-ng to checkout bzr repo via git. git-remote-bzr is part of git
> contrib scripts and is already shipped as part of git pkg in many distros
> (/usr/share/git/remote-helpers/git-remote-bzr in Arch Linux). I currently
> use grub bzr via git-remote-bzr.
> 

git-remote-bzr (and git-bzr-ng) are good to keep track of single
branch, but they won't replicate existing branches structure of bzr
repo. That will probably be the main problem. bzr and git use
sufficiently different work flow, so this will likely need to be done
manually (scripting).

git-remote-bzr does replicated all commits and stores branch tips,
which provides enough information to recreate branches in git. OTOH
with git often is using repo clones (which are really easy and cheap)
for what bzr is using branches. At least people/* branches are good
candidates for becoming separate repositories. 

I also do not know to which extent merge information is compatible
between git and bzr and whether this will preserve merge history,
assuming this is important.


  reply	other threads:[~2013-06-22 19:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-22 18:00 [RFC] Moving from Bazaar (bzr) to git Paul Menzel
2013-06-22 18:39 ` Keshav Padram
2013-06-22 19:40   ` Andrey Borzenkov [this message]
2013-06-22 21:52 ` Bruce Dubbs
2013-06-24 10:27   ` Mikko Rantalainen
2013-06-24 15:04     ` Daniel Kahn Gillmor
2013-06-25  2:54     ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-06-25  2:58       ` Gregg Levine
2013-06-24 14:09   ` Lennart Sorensen
2013-06-25  2:57     ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-06-25 14:16       ` Lennart Sorensen
2013-06-25  2:50 ` Geoffrey Thomas
2013-06-25 20:01   ` Darik Horn
2013-06-25 21:31     ` Geoffrey Thomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130622234031.2f886a3d@opensuse.site \
    --to=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.