From: Mikko Rantalainen <mikko.rantalainen@peda.net>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [RFC] Moving from Bazaar (bzr) to git
Date: Mon, 24 Jun 2013 13:27:05 +0300 [thread overview]
Message-ID: <51C81EF9.1020608@peda.net> (raw)
In-Reply-To: <51C61C84.8000901@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1599 bytes --]
Bruce Dubbs, 2013-06-23 00:52 (Europe/Helsinki):
> Paul Menzel wrote:
>> 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.)
>
> Personally, I prefer subversion, but I'm not a GRUB developer. The
> choice of version control can be similar emacs/vi or Bourne Shell/C
> Shell, so it really should be the choice of the primary developers.
I disagree. The choice of version control means a lot more than working
environment of a single developer (primary developer or not) because
that is the medium for sharing the source code. Even Linus himself uses
git over patches from email, even though the latter method is not bad
either for a single patch.
Once you master even a single DVCS system (e.g. Git, Mercurial, Bazaar),
the limitations caused by subversion or any other centralized version
control system start to look much greater than before.
I'd suggest trying to apply the workflow used by git development for
grub, too.
Make sure to have a mirror at github.com and if you don't want to use
github's issue tracker, put a big disclaimer about that in github. As
far as I know, you cannot disable public issue tracker in github
repository's settings.
--
Mikko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
next prev parent reply other threads:[~2013-06-24 10:27 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
2013-06-22 21:52 ` Bruce Dubbs
2013-06-24 10:27 ` Mikko Rantalainen [this message]
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=51C81EF9.1020608@peda.net \
--to=mikko.rantalainen@peda.net \
--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.