From: Karl Fogel <kfogel@red-bean.com>
To: Glenn Morris <rgm@gnu.org>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>,
"Juanma Barranquero" <lekktu@gmail.com>,
emacs-devel@gnu.org, "Alan Mackenzie" <acm@muc.de>
Subject: Re: Surely 'bzr update' shouldn't be this slow?
Date: Thu, 07 Jan 2010 15:48:00 -0500 [thread overview]
Message-ID: <87k4vtfxq7.fsf@red-bean.com> (raw)
In-Reply-To: <jevdfdg5w0.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 07 Jan 2010 12:51:43 -0500")
Glenn Morris <rgm@gnu.org> writes:
>Karl Fogel wrote:
>
>> Yes. I *think* we are having a savannah problem here, not a bzr
>> problem. People may find it faster to use the Launchpad.net mirror of
>> Emacs until Savannah gets bzr+ssh:// access (smart server).
>
>Have you tried asking rms to ask the Savannah admins to please make
>improving support for GNU bzr a high priority?
I've made similar requests of RMS before, and his response was:
"Mail the Savannah admins list and CC me."
which seems like a reasonable course of action.
Someone here want to do it?
next prev parent reply other threads:[~2010-01-07 20:48 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-03 17:47 Surely 'bzr branch' shouldn't be this slow? Alan Mackenzie
2010-01-03 17:59 ` Óscar Fuentes
2010-01-06 13:10 ` Alan Mackenzie
2010-01-06 13:28 ` Jason Rumney
2010-01-06 14:06 ` Óscar Fuentes
2010-01-06 18:23 ` Eli Zaretskii
2010-01-06 20:21 ` Stefan Monnier
2010-01-07 7:44 ` Yavor Doganov
2010-01-07 8:37 ` Lennart Borgman
2010-01-07 9:31 ` Juanma Barranquero
2010-01-07 19:18 ` Stephen Berman
2010-01-07 19:54 ` Eli Zaretskii
2010-01-07 20:09 ` Lennart Borgman
2010-01-07 21:48 ` Jason Earl
2010-01-07 23:48 ` Lennart Borgman
2010-01-08 2:07 ` Jason Earl
2010-01-08 7:10 ` Lennart Borgman
2010-01-08 8:13 ` Eli Zaretskii
2010-01-07 14:46 ` Stefan Monnier
2010-01-07 17:05 ` Yavor Doganov
2010-01-07 19:43 ` Stefan Monnier
2010-01-07 19:46 ` Lennart Borgman
2010-01-07 20:26 ` Thrashing [was: Surely 'bzr branch' shouldn't be this slow?] Stephen J. Turnbull
2010-01-07 20:20 ` Lennart Borgman
2010-01-07 13:40 ` Surely 'bzr update' shouldn't be this slow? [was: branch] Alan Mackenzie
2010-01-07 13:56 ` Surely 'bzr update' shouldn't be this slow? Óscar Fuentes
2010-01-07 14:03 ` Lennart Borgman
2010-01-07 15:18 ` Jan Djärv
2010-01-07 14:52 ` Alan Mackenzie
2010-01-07 15:00 ` Juanma Barranquero
2010-01-07 15:17 ` Karl Fogel
2010-01-07 17:51 ` Glenn Morris
2010-01-07 20:48 ` Karl Fogel [this message]
2010-01-07 21:21 ` Glenn Morris
2010-01-08 8:48 ` Eli Zaretskii
2010-01-07 15:17 ` Óscar Fuentes
2010-01-07 17:54 ` Stephen J. Turnbull
2010-01-07 15:06 ` Stefan Monnier
2010-01-06 14:37 ` Surely 'bzr branch' " Stefan Monnier
2010-01-07 5:00 ` Karl Fogel
-- strict thread matches above, loose matches on Subject: below --
2010-01-07 23:29 Surely 'bzr update' " grischka
2010-01-08 5:57 ` Stephen J. Turnbull
2010-01-08 17:49 ` grischka
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=87k4vtfxq7.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=ofv@wanadoo.es \
--cc=rgm@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).