From: Eli Zaretskii <eliz@gnu.org>
To: Christoph Scholtes <cschol2112@googlemail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs bzr access problems
Date: Tue, 02 Aug 2011 05:53:10 +0300 [thread overview]
Message-ID: <83aabsbk2x.fsf@gnu.org> (raw)
In-Reply-To: <4E375959.2010709@gmail.com>
> Date: Mon, 01 Aug 2011 19:56:41 -0600
> From: Christoph Scholtes <cschol2112@googlemail.com>
> CC: emacs-devel@gnu.org
>
> On 8/1/2011 2:29 PM, Eli Zaretskii wrote:
>
> > Please try again. I'm told that the problem should be solved.
>
> Works on Windows where the branch is only a couple of revisions behind.
>
> On GNU/Linux (Arch, bzr v2.3.4) where the trunk branch is at 104259 it
> starts pulling the revisions but after a while stops with the same error
> as before.
What protocol does this old branch use? (Look in
.bzr/branch/branch.conf if you don't remember.) Does the branch on
Windows use the same protocol?
next prev parent reply other threads:[~2011-08-02 2:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 17:59 Emacs bzr access problems Christoph Scholtes
2011-07-31 19:15 ` Antoine Levitt
2011-07-31 19:31 ` Eli Zaretskii
2011-07-31 20:04 ` Christoph Scholtes
2011-07-31 21:40 ` Antoine Levitt
2011-07-31 21:43 ` Christoph Scholtes
2011-07-31 21:58 ` Christoph Scholtes
2011-08-01 20:29 ` Eli Zaretskii
2011-08-01 21:05 ` Tuomo Hartikainen
2011-08-02 1:56 ` Christoph Scholtes
2011-08-02 2:53 ` Eli Zaretskii [this message]
2011-08-02 3:02 ` Christoph Scholtes
2011-08-02 5:45 ` Eli Zaretskii
2011-08-02 11:45 ` Christoph Scholtes
2011-08-02 16:40 ` Eli Zaretskii
2011-08-03 1:15 ` Christoph Scholtes
2011-08-09 17:54 ` Antoine Levitt
2011-08-10 6:10 ` Tim Cross
2011-08-10 6:13 ` Tim Cross
2011-08-10 7:52 ` Eli Zaretskii
2011-08-11 4:33 ` Eli Zaretskii
2011-08-14 3:06 ` Matt Curtis
2011-08-14 7:32 ` Eli Zaretskii
2011-08-14 7:47 ` Matt Curtis
2011-08-14 9:31 ` Thierry Volpiatto
2011-08-03 10:48 ` Andreas Röhler
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=83aabsbk2x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cschol2112@googlemail.com \
--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 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.