all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: SourceForge URLs changed
Date: Sun, 17 Jul 2016 23:40:24 +0200	[thread overview]
Message-ID: <87eg6s0wqf.fsf@elephly.net> (raw)
In-Reply-To: <20160717205826.GA9798@jasmine>


Leo Famulari <leo@famulari.name> writes:

> On Fri, Jul 15, 2016 at 10:58:00PM -0400, Leo Famulari wrote:
>> I can begin updating the URLs. It will be a good chance to stretch my
>> Guile a little bit. But, feel free to beat me to it :)
>
> There is just enough variety in the new URLs that I don't know how to
> approach it programmatically. So, I'm doing it by hand, which is not
> much fun. Please help :)

I read claims on the #guix IRC channel that the URLs appear to change
over time.  Has this been confirmed yet?  It would be sad if you or
others waste time on changing the URLs only to have them change yet
again.

~~ Ricardo

  reply	other threads:[~2016-07-17 21:40 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
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 [this message]
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=87eg6s0wqf.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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.