all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 49431@debbugs.gnu.org, Luis Felipe <luis.felipe.la@protonmail.com>
Subject: [bug#49431] [PATCH maintenance.git] nginx: berlin: Redirect old video URLs for each language.
Date: Sat, 10 Jul 2021 15:41:43 +0200	[thread overview]
Message-ID: <87a6mue160.fsf@gnu.org> (raw)
In-Reply-To: <20210709193844.dk4e7q5nanqe7iz7@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Fri, 9 Jul 2021 21:38:44 +0200")

Hi,

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

> Sorry for again asking such general questions.  A better question
> might be, should 'guix.gnu.org-redirects-for-each-language' go to a
> separate Guile module with a copyright header (if yes, what could it
> be named?), or remain in hydra/nginx/berlin.scm despite more complex
> code, without licensing information?

Let’s keep it in hydra/nginx/berlin.scm for now, and split in several
files later if we feel it’s becoming too messy.  (As for copyright, it’s
not even clear to me that a list of redirects is copyrightable per se
since it there’s only one way to do it.)

Ludo’.




  reply	other threads:[~2021-07-10 13:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-06  6:53 [bug#49431] [PATCH maintenance.git] nginx: berlin: Redirect old video URLs for each language pelzflorian (Florian Pelz)
2021-07-07 17:51 ` Luis Felipe via Guix-patches via
2021-07-08 13:53 ` Ludovic Courtès
2021-07-09  7:15   ` pelzflorian (Florian Pelz)
2021-07-09 19:38     ` pelzflorian (Florian Pelz)
2021-07-10 13:41       ` Ludovic Courtès [this message]
2021-07-10 10:27     ` Ludovic Courtès
2021-07-10 19:28       ` bug#49431: " pelzflorian (Florian Pelz)

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=87a6mue160.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=49431@debbugs.gnu.org \
    --cc=luis.felipe.la@protonmail.com \
    --cc=pelzflorian@pelzflorian.de \
    /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.