unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Karl Fogel <kfogel@red-bean.com>, emacs-devel@gnu.org
Subject: Re: What have the Romans done for us?  (Bazaar)
Date: Mon, 05 Apr 2010 15:44:50 -0400	[thread overview]
Message-ID: <jwvljd13d3d.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83vdc5yhsd.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 05 Apr 2010 19:40:18 +0300")

>> 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.

FWIW, it will be an improvement, but don't expect it to become
zippy either.

> 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".

Of course, this actually depends on what you define as "fully revert
a tree to a certain old revision".  If the intention is to undo the
changes since that revision, then "bzr revert -rNNN" is the right
answer, IIUC.  Whereas if you want to revert to revision NNN to
reproduce a bug there, then "bzr update -rNNN" is probably what
you want.

"bzr revert" is kind of like "cvs update -p", whereas "bzr update" is
kind of like "cvs update".


        Stefan




  reply	other threads:[~2010-04-05 19:44 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 [this message]
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=jwvljd13d3d.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=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).