all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: Julien Lepiller <julien@lepiller.eu>, 48187-done@debbugs.gnu.org
Subject: bug#48187: [PATCH] website: help: Add Guix's latest manual
Date: Tue, 4 May 2021 16:33:09 +0200	[thread overview]
Message-ID: <20210504143309.kuohokoadwsdlxmf@pelzflorian.localdomain> (raw)
In-Reply-To: <ADDgOPNqj8fgpRkJDsibGzX6LjPezCk96L27u33soI3J3VrB3IVpSOIGXxfNN2WylpEOPIpAg8Vv2QiHvPokS_oABrXod5xJiF5n_dms1Tg=@protonmail.com>

Pushed as f2152c8d76d59d4522ea3cf9a379d935338f57fa.

On Tue, May 04, 2021 at 02:00:43PM +0000, Luis Felipe wrote:
> Well, if that's legally suitable, it's fine by me, because, yes, I still waive all copyright interest on my contributions to the website :)

Probably it has legal weight (if not we’d have to change other files
too).  I’m not familiar enough with the difference between public
domain declarations and CC0 in the various jurisdictions.

> I think it's OK, Florian. Thanks for your help.

Thank you for all your contributions!

Regards,
Florian




      reply	other threads:[~2021-05-04 14:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03 14:07 [bug#48187] [PATCH] website: help: Add Guix's latest manual Luis Felipe via Guix-patches via
2021-05-03 15:15 ` Julien Lepiller
2021-05-03 15:43   ` Luis Felipe via Guix-patches via
2021-05-03 15:37 ` pelzflorian (Florian Pelz)
2021-05-03 16:27   ` Luis Felipe via Guix-patches via
2021-05-03 22:25     ` Julien Lepiller
2021-05-04  6:05     ` pelzflorian (Florian Pelz)
2021-05-04  6:37       ` pelzflorian (Florian Pelz)
2021-05-04 13:25         ` pelzflorian (Florian Pelz)
2021-05-04 14:00           ` Luis Felipe via Guix-patches via
2021-05-04 14:33             ` pelzflorian (Florian Pelz) [this message]

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=20210504143309.kuohokoadwsdlxmf@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=48187-done@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    --cc=luis.felipe.la@protonmail.com \
    /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.