All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Bazaar as main repository
Date: Sun, 8 Nov 2009 17:13:42 +0100	[thread overview]
Message-ID: <20091108161342.GA6803@thorin> (raw)
In-Reply-To: <4AE38810.3040707@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2327 bytes --]

On Sun, Oct 25, 2009 at 01:04:48AM +0200, Vladimir 'phcoder' Serbinenko wrote:
> Robert Millan wrote:
> > On Fri, Oct 23, 2009 at 04:40:06PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> >   
> >> What's preventing of using it as a main repository? This should allow
> >> easy resync
> >
> > Historically, it's been very hard for us to reach consensus on which revision
> > control system to use.  When we settled on SVN, it happened because we were
> > all fed up with CVS, not because it completely satisfied everyone.  In fact,
> > it was Bean who proposed it, even if he used GIT himself at the time!
> >
> > Other developers were unsatisfied with this decision, but chose not to object
> > to it just so we could get rid of CVS.
> >
> > Since a very wide consensus was reached, and it was so hard to archieve it,
> > I'm very reluctant to push for Bazaar as our trunk repository unless everyone
> > agrees this is what we want.
> >
> > Personally, I prefer if we did this switch, but I also think SVN does a good
> > job at managing a trunk.  I don't mind living with it for the time being.
> >
> > When I feel something is important, I don't hesitate to use my authority as
> > maintainer, but in this case I don't consider it necessary.  That said, if
> > I see consensus that we should switch to Bazaar as main repository, I won't
> > be the one to stop it.
> >
> >   
> Even though I'm git user and only bzr newbie, now when I started to
> learn it I like it and am for its adoption as main repo

Hi,

Vladimir would like to do this move;  I would like too, and can only assume
that Colin Watson would be satisfied with it.

So far nobody protested, and we finally sorted out the corruption problems.

I stop resyncing with SVN now.  All developers are encouraged to commit
directly to Bazaar (either trunk, experimental or personal branch depending
on the nature of changes).

Please remember to use sftp:// protocol, NOT bzr+ssh://.  If/when Savannah
upgrades their bzr daemon, we might consider using bzr+ssh:// in the future.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2009-11-08 16:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-22 20:32 bazaar mirror available Robert Millan
2009-10-23 14:40 ` Vladimir 'phcoder' Serbinenko
2009-10-24 12:36   ` Robert Millan
2009-10-24 23:04     ` Vladimir 'phcoder' Serbinenko
2009-11-08 16:13       ` Robert Millan [this message]
2009-11-09 15:49         ` Bazaar as main repository Michal Suchanek
2009-11-09 16:02           ` Robert Millan
2009-11-09 16:16             ` Michal Suchanek
2009-11-09 16:35           ` Felix Zielcke

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=20091108161342.GA6803@thorin \
    --to=rmh@aybabtu.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.