From: Tim Cross <theophilusx@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: bzr not working?
Date: Mon, 10 Oct 2011 19:00:34 +1100 [thread overview]
Message-ID: <CAC=50j9HG-s=bGjggGcUfDzgDhPrZf1jD1+A=MXYhfpT_OQSdQ@mail.gmail.com> (raw)
In-Reply-To: <E1RDAS2-0008Rk-5H@fencepost.gnu.org>
On Mon, Oct 10, 2011 at 6:39 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Mon, 10 Oct 2011 17:08:54 +1100
>> From: Tim Cross <theophilusx@gmail.com>
>> Cc: emacs-devel@gnu.org
>>
>> OK, so that makes two who can issue the same command as me and it
>> would seem only me who cannot.
>
> I "succeeded" to reproduce this on one machine to which I have
> access. So you are not alone. Posted the info to
> savannah-hackers-public.
>
Got home and tried it on my home machine. Exactly same setup, using 64
bit xubuntu instead of 32 bit and all works fine with no problems! On
the other machine, I was able to access other bzr repositories i.e.
the VM repo on launchpad, with no problems, so whatever the issue is,
it seems specific to the emacs repo on savannah (and maybe other bzr
repos on savannah???).
Will try your diagnostic suggestions tomorrow when I return to work.
Thanks for the help and thanks for indicating that perhaps its not
just me!
Tim
--
Tim Cross
Phone: 0428 212 217
next prev parent reply other threads:[~2011-10-10 8:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 22:24 bzr not working? Tim Cross
2011-10-09 22:41 ` Carsten Mattner
2011-10-09 23:13 ` Tim Cross
2011-10-10 3:56 ` Eli Zaretskii
2011-10-10 5:01 ` Tim Cross
2011-10-10 5:59 ` Eli Zaretskii
2011-10-10 6:08 ` Tim Cross
2011-10-10 6:41 ` Eli Zaretskii
2011-10-10 7:39 ` Eli Zaretskii
2011-10-10 8:00 ` Tim Cross [this message]
2011-10-10 8:27 ` Eli Zaretskii
2011-10-10 11:53 ` Tim Cross
2011-10-11 23:35 ` Tim Cross
2011-10-12 8:43 ` Eli Zaretskii
2011-10-12 23:13 ` Tim Cross
2011-10-19 21:33 ` Tim Cross
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='CAC=50j9HG-s=bGjggGcUfDzgDhPrZf1jD1+A=MXYhfpT_OQSdQ@mail.gmail.com' \
--to=theophilusx@gmail.com \
--cc=eliz@gnu.org \
--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 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).