all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: David Reitter <david.reitter@gmail.com>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>,
	"Eric M. Ludlam" <eric@siege-engine.com>
Subject: Re: [CEDET-devel] Switching CEDET from CVS to a Distributed VCS.
Date: Thu, 25 Jun 2009 10:44:50 +0200	[thread overview]
Message-ID: <e01d8a50906250144q28f28eadhfc4493ee34a8bdef@mail.gmail.com> (raw)
In-Reply-To: <393CA42E-4553-4F2D-92D8-F0D3CEE19223@gmail.com>

On Thu, Jun 25, 2009 at 5:23 AM, David Reitter<david.reitter@gmail.com> wrote:
> On Jun 24, 2009, at 6:45 PM, Lennart Borgman wrote:
>
>> Hi Eric,
>>
>> I think I have said it before, but I believe it is worth saying again:
>> Emacs repository will be moved from CVS to Bazaar. And since CEDET is
>> going to be included in Emacs you will most likely be using Bazaar
>> after that.
>>
>> Alex, as I said before I do not know much at all about version control
>> system. However even from my limited understanding of this I still
>> can't find room for arguments for using something else than Bazaar for
>> CEDET. Will not using something else than Bazaar put an extra burdon
>> on Eric? And I guess that is what we all want to avoid ... ;-)
>
> If it helps others over at Cedet:
>
> I evaluated Bazaar over the course of 6 months for Aquamacs (which
> incorporates the full Emacs repository).  Using Bazaar with this repository
> (and coming up with a workable conversion of Aquamacs and Emacs CVSes) was
> endless pain, frustration and bug reporting (starting with cryptic error
> messages from the bowels of Bzr).
>
> Bzr is well-meant and its UI is well-designed, but it lacks the efficiency
> and reliability to manage a repository with >100k revisions.   It lacks a
> quality assurance process (with its monthly release cycle that's difficult)
> and reliable error signaling / integrity checking (its ever-changing
> repository formats are not seamless at all w.r.t. transitions).  It is
> dog-slow with a large repository, even with the latest changes to "bzr log".



Thanks David, hope you do not mind I am sending this along to Emacs Devel.

Are these problems still there? In that case they might be very
important for the time scale when switching Emacs to using Bazaar.



> Git has been painless and elegant.   Nothing gets in your way.
>
> All that said, I tried very hard to make Bzr work for us and spent a lot of
> time dealing with bugs, precisely for the reasons that Lennart stated.
>
> For a smaller repository, Bzr may well work, especially if you don't import
> a "messed up" CVS repo with many branches.
>
> (Otherwise, it seems that a lot of Emacs dev's use Git to manage their work
> privately before transferring their changes into the Emacs repository.)




  parent reply	other threads:[~2009-06-25  8:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1245882173.24086.14.camel@projectile.siege-engine.com>
2009-06-24 22:45 ` Switching CEDET from CVS to a Distributed VCS Lennart Borgman
2009-06-24 23:51   ` Eric M. Ludlam
2009-06-25  2:40   ` Miles Bader
2009-06-25 13:52     ` David Bernard
2009-06-25 16:04       ` [CEDET-devel] " Davi Diaz
2009-06-26  0:09         ` Miles Bader
2009-06-25 17:48     ` Stephen J. Turnbull
2009-06-25 18:24       ` David Reitter
2009-06-28  6:17         ` Stephen J. Turnbull
2009-06-28 11:45           ` David Reitter
2009-06-28 14:04             ` Stephen J. Turnbull
2009-06-28 14:29               ` David Reitter
2009-06-29 23:19                 ` Stephen J. Turnbull
2009-06-30  0:16                   ` David Reitter
     [not found]   ` <393CA42E-4553-4F2D-92D8-F0D3CEE19223@gmail.com>
2009-06-25  8:44     ` Lennart Borgman [this message]
2009-06-25 12:53       ` [CEDET-devel] " Stefan Monnier
2009-06-25 13:19       ` David Reitter

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=e01d8a50906250144q28f28eadhfc4493ee34a8bdef@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=david.reitter@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=eric@siege-engine.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.