unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: What have the Romans done for us?  (Bazaar)
Date: Mon, 5 Apr 2010 14:56:37 +0000	[thread overview]
Message-ID: <20100405145637.GA3248@muc.de> (raw)

Hi, Emacs,

Would somebody please remind me of all the advantages Bazaar has over
CVS, all the wonderful things it enables one to do.

Right at the moment, it just seems like a slow, slow, slow and buggy
replacement for CVS, which consumes several hundred megabytes of my disk
space more than CVS did.  There doesn't seem to be a bzr equivalent of
http://cvs.savannah.gnu.org/viewcv; bzr log is so slow (40 seconds) as
to be only somewhat useful.  Even updating one's repository takes many
minutes, something which took only a few seconds with CVS.  Worst of all
is the lack of a proper fine manual; what there is is available only in
html or "bzr help", neither of which is properly searchable; what there
is is also bloated and vague and generally of low quality.

At Stefan's suggestion, I tried

  $ bzr diff -r tag:EMACS_23_1 lisp/progmodes/cc-*.el

.  This crashes bzr.  I've just updated to the latest version of bzr
(2.1.0), and it still crashes.  So keen are bzr's developers to get
decent bug reports that they make you register (on "launchpad") before
they'll deign to permit you to submit one.  They insist on you
submitting this bug report via a script running in a web-browser.  That
script fails on my machine, so I'm stuffed.  Anybody know a mail address
to get in touch with the bazaar team?

So, yes, bzr is wonderful, because it's a DISTRIBUTED VCS, and
distributed VCSs are Good Things.  Would somebody please remind me why?

Thanks!

-- 
Alan Mackenzie (Nuremberg, Germany).




             reply	other threads:[~2010-04-05 14:56 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 14:56 Alan Mackenzie [this message]
2010-04-05 15:32 ` What have the Romans done for us? (Bazaar) Karl Fogel
2010-04-05 16:08   ` Andreas Schwab
2010-04-05 20:54     ` Karl Fogel
2010-04-05 21:11       ` Andreas Schwab
2010-04-05 21:19         ` Andreas Schwab
2010-04-05 16:40   ` Eli Zaretskii
2010-04-05 19:44     ` Stefan Monnier
2010-04-05 22:01       ` Eli Zaretskii
2010-04-05 20:56     ` Karl Fogel
2010-04-05 19:39   ` Óscar Fuentes
2010-04-06 14:31   ` Alan Mackenzie
2010-04-06 15:24     ` Andreas Schwab
2010-04-06 17:02     ` Chad Brown
2010-04-06 19:50       ` Juri Linkov
2010-04-07  6:33     ` Eli Zaretskii
2010-04-07 18:47     ` Stephen J. Turnbull
2010-04-05 15:34 ` Eli Zaretskii
2010-04-05 15:43   ` Andreas Schwab
2010-04-05 16:42     ` Eli Zaretskii
2010-04-05 19:52     ` Stefan Monnier
2010-04-06 10:43     ` Richard Stallman
2010-04-07 18:11       ` Stephen J. Turnbull
2010-04-05 16:01 ` Chad Brown
2010-04-05 19:56   ` Stefan Monnier
2010-04-05 23:06     ` chad
2010-04-06  7:14       ` Stephen J. Turnbull
2010-04-05 16:12 ` Chong Yidong
2010-04-06 10:43 ` Richard Stallman
2010-04-06 13:25   ` Alan Mackenzie
2010-04-12  5:04     ` Martin Pool
2010-04-06 14:35 ` Jason Rumney
2010-04-06 16:20   ` Alan Mackenzie
2010-04-07 18:21     ` Stephen J. Turnbull
2010-04-07 20:38 ` Óscar Fuentes

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=20100405145637.GA3248@muc.de \
    --to=acm@muc.de \
    --cc=emacs-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.
Code repositories for project(s) associated with this public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).