unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: bazaar: "unable to obtain lock"
Date: Fri, 01 Jan 2010 11:16:34 +0100	[thread overview]
Message-ID: <87vdfmi0zh.fsf@telefonica.net> (raw)
In-Reply-To: 87fx6qno26.fsf@uwakimon.sk.tsukuba.ac.jp

"Stephen J. Turnbull" <stephen@xemacs.org> writes:

> Kevin Ryde writes:
>
>  > Karl Fogel <kfogel@red-bean.com> writes:
>  > >
>  > >   http://www.red-bean.com/kfogel/emacs-bzr-repository.tar.gz
>  > 
>  > Is anything smaller possible for those of us at the end of a straw?
>  > I see BzrQuickStartForEmacsDevs advises 300mb similarly.  Is some sort
>  > of small no-history checkout possible?
>
> It's possible, but AFAIK not without a smart server at the other end.
> This is being worked on, but it's a Savannah issue with no ETA last I
> heard, not an Emacs or Bazaar issue.  For status on this, see
> https://savannah.gnu.org/support/?107077.

I don't think that the smart server would significantly reduce the
amount of transferred data for the first branch. What it can save is the
chit-chat associated with the sftp/http (IIRC http is worse than sftp.)
This can have a noticeable impact on the time required by the operation,
but if you are using a 56kb/s dialup connection, the 200+ MB of history
will hurt anyway.

> Óscar mentioned "lightweight checkout", but as I understand it this
> may involve downloading the whole repo anyway, since actually
> extracting files from the archive storage is done by your local bzr.

I was referring to the possibility of creating a tarball with a
lightweight checkout (this subthread is about the tarball containing the
initial setup, see above.) This tarball would be 31 MB, but the question
is if there is enough demand to justify it, or even if it makes sense:
if you are so desperate about bandwidth, day-to-day work with bazaar
will be *very* painful until someone setups a smart server as you
suggest.

[snip]

-- 
Óscar





  reply	other threads:[~2010-01-01 10:16 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
2010-01-01  9:59     ` Stephen J. Turnbull
2010-01-01 10:16       ` Óscar Fuentes [this message]
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=87vdfmi0zh.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --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).