unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: What have the Romans done for us?  (Bazaar)
Date: Mon, 05 Apr 2010 18:34:26 +0300	[thread overview]
Message-ID: <83zl1hyku5.fsf@gnu.org> (raw)
In-Reply-To: <20100405145637.GA3248@muc.de>

> Date: Mon, 5 Apr 2010 14:56:37 +0000
> From: Alan Mackenzie <acm@muc.de>
> 
> 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.

Try "bzr log --line -l100" instead (replace 100 with a larger number
if you want to look farther back).  This takes about 3 seconds on my
box with a cold cache, 1 sec with a warm cache.

> Even updating one's repository takes many minutes, something which
> took only a few seconds with CVS.

Which reminds me: any chance to get bzr+ssh "smart server" any time in
this millenium?

> At Stefan's suggestion, I tried
> 
>   $ bzr diff -r tag:EMACS_23_1 lisp/progmodes/cc-*.el
> 
> .  This crashes bzr.

It throws a fatal error because it does not find some revision it
thought it should:

  bzr: ERROR: bzrlib.errors.NoSuchRevision: CHKInventoryRepository('file:///D:/gnu/bzr/emacs/.bzr/repository/') has no revision ('cyd@stupidchicken.com-20090730011415-1ur84cd4r2dats1v',)

"bzr revision-info cyd@stupidchicken.com-20090730011415-1ur84cd4r2dats1v" 
indeed does not find such a revision neither on the trunk nor on the
emacs-23 branch.  What is that revision, and why did it disappear?
Does it mean our repository is corrupted?

> Anybody know a mail address to get in touch with the bazaar team?

  mailto:bazaar@lists.canonical.com




  parent reply	other threads:[~2010-04-05 15:34 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 14:56 What have the Romans done for us? (Bazaar) Alan Mackenzie
2010-04-05 15:32 ` 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 [this message]
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=83zl1hyku5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=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).