From: Kevin Ryde <user42@zip.com.au>
To: emacs-devel@gnu.org
Subject: Re: bazaar: "unable to obtain lock"
Date: Wed, 06 Jan 2010 08:20:57 +1100 [thread overview]
Message-ID: <878wccuu2u.fsf@blah.blah> (raw)
In-Reply-To: <E1NRh0e-0002kF-IR@fencepost.gnu.org> (Eli Zaretskii's message of "Mon, 04 Jan 2010 02:05:48 -0500")
Eli Zaretskii <eliz@gnu.org> writes:
>
> For
> example, today's "bzr up" crams 185MB(!) of data through the wire.
Strewth.
> So I'm not sure if we should tell anything about traffic beyond the
> initial branch, whose size is more or less known and changes very
> slowly.
Well, at least somehow that it's much more than the size of a "diff"!
next prev parent reply other threads:[~2010-01-05 21:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 23:53 bazaar: "unable to obtain lock" Robert J. Chassell
2009-12-30 3:39 ` Karl Fogel
2009-12-30 15:15 ` Robert J. Chassell
2009-12-31 19:14 ` Karl Fogel
2010-01-01 0:19 ` Robert J. Chassell
2009-12-31 19:15 ` Karl Fogel
2009-12-30 16:43 ` Robert J. Chassell
2009-12-30 17:25 ` Andreas Schwab
2009-12-30 21:46 ` Robert J. Chassell
2009-12-30 22:18 ` Andreas Schwab
2009-12-31 1:48 ` Robert J. Chassell
2009-12-31 4:29 ` Óscar Fuentes
2009-12-31 6:59 ` Óscar Fuentes
2009-12-31 11:32 ` Robert J. Chassell
2009-12-31 14:57 ` James Cloos
2009-12-30 23:34 ` Kevin Ryde
2009-12-31 0:30 ` Óscar Fuentes
2009-12-31 0:44 ` Lennart Borgman
2009-12-31 1:07 ` Óscar Fuentes
2009-12-31 1:24 ` Lennart Borgman
2010-01-03 22:38 ` Kevin Ryde
2010-01-04 7:05 ` Eli Zaretskii
2010-01-05 21:20 ` Kevin Ryde [this message]
2010-01-01 9:59 ` Stephen J. Turnbull
2010-01-01 10:16 ` Óscar Fuentes
2010-01-01 16:42 ` Jason Earl
2009-12-30 9:19 ` David Kastrup
-- strict thread matches above, loose matches on Subject: below --
2009-12-29 17:14 Juanma Barranquero
2009-12-29 17:40 ` Karl Fogel
2009-12-29 17:44 ` Juanma Barranquero
2009-12-29 18:42 ` Karl Fogel
2009-12-29 20:39 ` 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=878wccuu2u.fsf@blah.blah \
--to=user42@zip.com.au \
--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).