unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Karl Fogel <kfogel@red-bean.com>
Cc: emacs-devel@gnu.org
Subject: Re: What have the Romans done for us?  (Bazaar)
Date: Mon, 05 Apr 2010 19:40:18 +0300	[thread overview]
Message-ID: <83vdc5yhsd.fsf@gnu.org> (raw)
In-Reply-To: <87mxxhhq3b.fsf@red-bean.com>

> From: Karl Fogel <kfogel@red-bean.com>
> Date: Mon, 05 Apr 2010 11:32:56 -0400
> Cc: emacs-devel@gnu.org
> 
> > Even updating one's repository takes many
> >minutes, something which took only a few seconds with CVS.
> 
> Yes.  But remember: https://savannah.gnu.org/support/?107077
> (which is actively being worked on).

Thanks.  Any ETA?  It's really annoying to wait 2-3 minutes each time
I do a simple "bzr up", and similarly for "bzr ci" to the public
repository.

> >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.
> 
> ?  http://doc.bazaar.canonical.com/en/ points to plenty of downloadable
> documentation, in HTML, CHM, and PDF formats.

Well, yes, but the quality of the Bazaar docs leaves a lot to be
desired.  E.g., I just learned (through a question posted to the
Bazaar list) that to fully revert a tree to a certain old revision,
one needs to do a "bzr update -rNNN" rather than "bzr revert -rNNN".
There's nothing about this important fact in the Bazaar User Reference
Guide.




  parent reply	other threads:[~2010-04-05 16:40 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 [this message]
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=83vdc5yhsd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kfogel@red-bean.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 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).