all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Griffin <a@ajgrf.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: SourceForge URLs changed
Date: Fri, 15 Jul 2016 10:28:13 -0500	[thread overview]
Message-ID: <1468596493.1316361.667333481.4DA63202@webmail.messagingengine.com> (raw)
In-Reply-To: <87shvdn8r2.fsf@gnu.org>

On Wed, Jul 13, 2016, at 05:16 AM, Ludovic Courtès wrote:
> Alex Griffin <a@ajgrf.com> skribis:
> > Their Twitter feed[1] says that they're investigating issues at the
> > moment, so it's possible that all we need to do is wait.
> 
> OK, we’ll see.

So it has been a few days now, and it looks like I was probably wrong.
I'm a little baffled that I couldn't find any other free software
communities talking about this either, since I would have guessed a
disruptive change like this would have affected other distros that
automate source downloads (like NixOS, Arch Linux, Gentoo, etc.)
-- 
Alex Griffin

  reply	other threads:[~2016-07-15 15:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-12 23:00 SourceForge URLs changed Ludovic Courtès
2016-07-12 23:37 ` Alex Griffin
2016-07-13 10:16   ` Ludovic Courtès
2016-07-15 15:28     ` Alex Griffin [this message]
2016-07-15 17:58       ` Leo Famulari
2016-07-15 18:15         ` Alex Griffin
2016-07-16 12:17           ` Ludovic Courtès
2016-07-16  2:58 ` Leo Famulari
2016-07-16  3:00   ` Leo Famulari
2016-07-17 20:58   ` Leo Famulari
2016-07-17 21:40     ` Ricardo Wurmus
2016-07-17 21:50       ` Leo Famulari
2016-07-18 18:30     ` Alex Griffin
2016-07-18 22:21       ` Leo Famulari
2016-07-21 14:33   ` Leo Famulari
2016-07-21 15:32     ` Andreas Enge
2016-07-21 16:34       ` Ludovic Courtès
2016-07-21 20:41     ` Alex Griffin
2016-07-21 22:13       ` Leo Famulari

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1468596493.1316361.667333481.4DA63202@webmail.messagingengine.com \
    --to=a@ajgrf.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.