unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "alin.s" <alinsoar@voila.fr>,
	Giuseppe Scrivano <gscrivano@gnu.org>,
	Drew Adams <drew.adams@oracle.com>,
	Emacs-devel@gnu.org
Subject: Re: http access to source code
Date: Thu, 22 Jul 2010 18:08:37 +0200	[thread overview]
Message-ID: <AANLkTim3SYdRDZmqgvic0LJxlTw4clr1NC5Qj88fgwFd@mail.gmail.com> (raw)
In-Reply-To: <jwv4ofrtws0.fsf-monnier+emacs@gnu.org>

On Thu, Jul 22, 2010 at 4:32 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> This sorry sorry-thank-you page has been thanking us for our patience for a
>> _very_ long time now.
>
> Have you tried to access that page a few times in a row.  I've seen this
> message as well, but if I retry right away, it usually works (my mental
> model to explain it: the Emacs repository is so large that it takes too
> long to swap it in, so the webserver timeouts and gives an error even
> though the operation actually works fine, so if you try it again right
> away, it can work because some of the data is already swapped in and
> the whole process can then finish before the timeout).


So you mean that the whole tree structure has to be swapped in to
access a single directory or file? Is that the web server interface of
bazaar that has this kind of problem?

I would guess that the problem is within bazaar (because of
optimizations perhaps have been made against single goals there, but
this is just my guess). In that case the cure would be caching the
tree structure.



  parent reply	other threads:[~2010-07-22 16:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 14:49 http access to source code Drew Adams
2010-04-05 14:55 ` Karl Fogel
2010-04-05 15:05   ` Drew Adams
2010-04-05 15:39     ` Karl Fogel
2010-04-05 15:59       ` Drew Adams
2010-05-16 22:02         ` Drew Adams
2010-05-16 22:36           ` alin.s
2010-05-16 22:41             ` Giuseppe Scrivano
2010-05-16 22:51               ` Drew Adams
2010-05-16 22:57                 ` Lennart Borgman
2010-05-16 22:59                 ` alin.s
2010-07-15 15:03                 ` Drew Adams
2010-07-15 15:13                   ` Chong Yidong
2010-07-15 15:24                     ` Drew Adams
2010-07-15 15:14                   ` René Kyllingstad
2010-07-15 16:57                     ` Drew Adams
2010-07-22 14:32                   ` Stefan Monnier
2010-07-22 15:26                     ` Drew Adams
2010-07-22 16:08                     ` Lennart Borgman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-07-15 15:27 A. Soare
2010-07-15 15:30 A. Soare
2010-07-15 15:37 ` Chong Yidong
2010-07-15 15:45   ` Drew Adams
2010-07-15 16:09     ` Chong Yidong
2010-07-15 15:41 ` Drew Adams

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=AANLkTim3SYdRDZmqgvic0LJxlTw4clr1NC5Qj88fgwFd@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=Emacs-devel@gnu.org \
    --cc=alinsoar@voila.fr \
    --cc=drew.adams@oracle.com \
    --cc=gscrivano@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).