unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "René Kyllingstad" <listmailemacs@kyllingstad.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Emacs-devel@gnu.org
Subject: Re: http access to source code
Date: Thu, 15 Jul 2010 17:14:22 +0200	[thread overview]
Message-ID: <AANLkTikRYuaueUNQkoNyE-pEE079p3HxHhqLZQec5l02@mail.gmail.com> (raw)
In-Reply-To: <C9138B4F02DB417F83361915FD0AD759@us.oracle.com>

On Thu, Jul 15, 2010 at 5:03 PM, Drew Adams <drew.adams@oracle.com> wrote:
>> Sent: Sunday, May 16, 2010 3:51 PM
>> > Here the same, on the first attempt.
>> >
>> > > This is the output for me
>> > >
>> > >  Please try again
>> > >
>> > >  Sorry, there was a problem connecting to the Launchpad server.
>> > >
>> > >  Try reloading this page in a minute or two. If the problem
>> > >  persists, let us know in the #launchpad IRC channel on Freenode.
>> > >
>> > >  Thanks for your patience.
>>
>> Well at least I'm glad to see someone else sees the same
>> thing I do.  I see this almost all the time.  I don't use IRC.
>> Perhaps someone else will report it.  But I would be surprised
>> if they weren't aware of it.  It's been like this forever.
>
> This sorry sorry-thank-you page has been thanking us for our patience for a
> _very_ long time now.  Is there at least a plan to do something about this?
> HTTP access to the source code is nearly non-existent (/dev/null-like), and it
> has been this way since the changeover to BZR.

This works for me right now:

    http://bazaar.launchpad.net/~vcs-imports/emacs/trunk/files


-- René



  parent reply	other threads:[~2010-07-15 15:14 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 [this message]
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
  -- 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=AANLkTikRYuaueUNQkoNyE-pEE079p3HxHhqLZQec5l02@mail.gmail.com \
    --to=listmailemacs@kyllingstad.com \
    --cc=Emacs-devel@gnu.org \
    --cc=drew.adams@oracle.com \
    /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).