From: Karl Fogel <kfogel@red-bean.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Juanma Barranquero <lekktu@gmail.com>, emacs-devel@gnu.org
Subject: Re: Strange message from "bzr pull"
Date: Tue, 29 Dec 2009 12:00:11 -0500 [thread overview]
Message-ID: <877hs5ogv8.fsf@red-bean.com> (raw)
In-Reply-To: <E1NPern-0005aX-L0@fencepost.gnu.org> (Eli Zaretskii's message of "Tue, 29 Dec 2009 11:24:15 -0500")
Eli Zaretskii <eliz@gnu.org> writes:
>> Have you installed the repo anew after the switchover?
>
>Yes. (The previous one was on another box, anyway.)
>
>> AFAIK, the M means that the working copy file has been updated. The
>> original instructions had the trunk created with
>>
>> bzr branch --no-tree sftp://...
>>
>> so trunk/ had no working copy. Karl changed that perhaps two weeks ago.
>
>You are right, thanks for unlocking the mystery.
>
>But why were these instructions changed? I thought having the trunk
>treeless had some clear advantages, the physical impossibility of
>editing there being one of them.
>
>Karl?
I changed it because in actually testing the instructions, I discovered
that the old instructions did not work :-). Here is the revision
message from the wiki:
2009-12-07 19:47 UTC Revision 56 (KarlFogel)
====================================================================
Remove the --no-tree recommendation for the local trunk mirror. In
order for merging into trunk (from local development branches) to
work, there has to be a working tree in the merge
destination. Otherwise you will get an error like, e.g., 'bzr: ERROR:
No WorkingTree exists for
"file:///home/kfogel/src/emacs/trunk/.bzr/checkout/".'
-Karl
next prev parent reply other threads:[~2009-12-29 17:00 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877hs5ogv8.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.