unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: kfogel@red-bean.com, emacs-devel@gnu.org
Subject: Re: Strange message from "bzr pull"
Date: Wed, 30 Dec 2009 10:05:53 -0500	[thread overview]
Message-ID: <E1NQ07V-0004YQ-TV@fencepost.gnu.org> (raw)
In-Reply-To: <f7ccd24b0912300419u1fe6603cg52caaf735b1977c2@mail.gmail.com> (message from Juanma Barranquero on Wed, 30 Dec 2009 13:19:43 +0100)

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Wed, 30 Dec 2009 13:19:43 +0100
> Cc: kfogel@red-bean.com, emacs-devel@gnu.org
> 
> On Wed, Dec 30, 2009 at 08:02, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> > If so, perhaps it's better to say on the wiki that
> > "bzr update" be always used in trunk/, because it will always work, no
> > matter if the mirror diverged or not?
> 
> If you look at the archives of the Bazaar list, there's a thread "bzr
> pull vs. bzr update" starting on Dec 16 where the issue is discussed
> (specifically with respect to Emacs and the BzrForEmacsDevs document).

Thanks for the pointer.

After reading that, I think that the Emacswiki should recommend "bzr up",
not "bzr pull".  The main reason is that the Bazaar docs say one should
use `update' in this configuration.  Bazaar docs are far from ideal,
but they are very clear on this issue.  It doesn't make sense, IMO, to
confuse newcomers to Bazaar by going against the user manual, especially
if we want to save them from extra confusion.

Besides, with the trunk not treeless anymore, the chances that one-off
changes will be done there just became higher, and with them the risk
of having "bzr pull" error out ==> more confusion, and IMO for no good
reason.




  reply	other threads:[~2009-12-30 15:05 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29  7:43 Strange message from "bzr pull" Eli Zaretskii
2009-12-29 10:18 ` Juanma Barranquero
2009-12-29 10:30   ` Eli Zaretskii
2009-12-29 12:40     ` Juanma Barranquero
2009-12-29 16:24       ` Eli Zaretskii
2009-12-29 17:00         ` Karl Fogel
2009-12-29 18:10           ` Eli Zaretskii
2009-12-29 18:13             ` Juanma Barranquero
2009-12-29 18:34               ` Eli Zaretskii
2009-12-29 19:28                 ` Óscar Fuentes
2009-12-29 19:51                   ` Karl Fogel
2009-12-29 20:04                     ` Óscar Fuentes
2009-12-29 20:15                       ` Karl Fogel
2009-12-29 20:29                       ` Eli Zaretskii
2009-12-29 23:32                         ` Óscar Fuentes
2009-12-30  4:16                           ` Eli Zaretskii
2009-12-30  5:15                             ` Óscar Fuentes
2009-12-31  9:39                       ` Stephen J. Turnbull
2009-12-29 20:16                   ` Eli Zaretskii
2009-12-29 23:14                     ` Óscar Fuentes
2009-12-30  4:21                       ` Eli Zaretskii
2009-12-30  4:28                         ` Miles Bader
2009-12-30  5:26                         ` Óscar Fuentes
2009-12-29 18:44             ` Karl Fogel
2009-12-29 19:01               ` Eli Zaretskii
2009-12-29 19:09                 ` Karl Fogel
2009-12-29 20:09                   ` Eli Zaretskii
2009-12-30  7:02                     ` Eli Zaretskii
2009-12-30 12:19                       ` Juanma Barranquero
2009-12-30 15:05                         ` Eli Zaretskii [this message]
2009-12-30 15:19                           ` Juanma Barranquero
2009-12-31 19:36                           ` Karl Fogel
2009-12-31 20:49                             ` Juanma Barranquero
2009-12-29 21:37                 ` Stefan Monnier
2009-12-31  9:43                   ` Stephen J. Turnbull
2009-12-29 18:02       ` Eli Zaretskii
2009-12-29 18:12         ` Juanma Barranquero

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=E1NQ07V-0004YQ-TV@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kfogel@red-bean.com \
    --cc=lekktu@gmail.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).