From: ng0 <ng0@we.make.ritual.n0.is>
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 17:08:13 +0000 [thread overview]
Message-ID: <20160611170813.GA3959@khazad-dum> (raw)
In-Reply-To: <87d1nnofcb.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1838 bytes --]
On 2016-06-11(06:33:24PM+0200), Mathieu Lirzin wrote:
> 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.
I can see if I can revert this, logically it fitted into the same box
for me as the previous url rewrite patches I did send in,
the protocol used changed, not the entire URL.
Those covered 1 file per patch, which wasn't possible with this
one neither did it look logical to me.
> > 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
I will do that, thanks for pointing it out to me.
The last 2 patches might have included this change too, could you
or someone else check up on them?
I will write an email to GNU now with an reference to this post
and inquire about the change.
--
♥Ⓐ ng0
For non-prism friendly talk find me on
psyced.org / loupsycedyglgamf.onion
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2016-06-11 17:08 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
2016-06-11 17:08 ` ng0 [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160611170813.GA3959@khazad-dum \
--to=ng0@we.make.ritual.n0.is \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).