all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu Lirzin <mthl@gnu.org>
To: guix-devel@gnu.org
Subject: Re: [PATCH] for gnu/packages/*.scm rewrite http to https for gnu.org, emacs.scm: add tls for elpa (https://elpa.gnu.org)
Date: Sat, 11 Jun 2016 18:33:24 +0200	[thread overview]
Message-ID: <87d1nnofcb.fsf@gnu.org> (raw)
In-Reply-To: <20160611155519.GA24412@khazad-dum> (ng0@we.make.ritual.n0.is's message of "Sat, 11 Jun 2016 15:55:20 +0000")

Hello,

ng0 <ng0@we.make.ritual.n0.is> writes:

> Hi, last cosmetic patch for today.
> This patch does the following:
>
> 1. rewrite every occurence in gnu/packages/*.scm files of
>    http://www.gnu.org to https://www.gnu.org
> 2. for gnu/packages/emacs.scm enable tls for elpa.gnu.org,
>    which is now using a certificate by the LetsEncrypt CA.

I think one patch for each of these 2 changes would be better.

> From 389e846deaa379ca10b5d006afa26693dc0085d8 Mon Sep 17 00:00:00 2001
> From: ng0 <ng0@we.make.ritual.n0.is>
> Date: Sat, 11 Jun 2016 15:32:07 +0000
> Subject: [PATCH] gnu: gnu/packages/().scm: URL http->https corrections.

I have noticed that this patch modifies the copying permission statement
too.  Since they are copied from
<https://www.gnu.org/licenses/gpl-howto.html>, I think it would be
preferable to modify the original before.

Could you ask <gnu@gnu.org> to apply this change on the website first
and then make a separate patch for making Guix conform to it?

Sorry for these administrative boredoms.  :)

Thanks,

-- 
Mathieu Lirzin

  reply	other threads:[~2016-06-11 16:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-11 15:55 [PATCH] for gnu/packages/*.scm rewrite http to https for gnu.org, emacs.scm: add tls for elpa (https://elpa.gnu.org) ng0
2016-06-11 16:33 ` Mathieu Lirzin [this message]
2016-06-11 17:08   ` ng0
2016-06-16 17:18     ` Mathieu Lirzin
2016-06-11 17:48   ` ng0
2016-08-08 21:56     ` ng0

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=87d1nnofcb.fsf@gnu.org \
    --to=mthl@gnu.org \
    --cc=guix-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 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.