From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Stefan Baums <baums@stefanbaums.com>, 54783@debbugs.gnu.org
Cc: Josselin Poiret <dev@jpoiret.xyz>
Subject: bug#54783: [PATCH 2/2] doc: Remove double copyright.
Date: Thu, 21 Apr 2022 15:49:21 +0200 [thread overview]
Message-ID: <20220421134921.1505-2-dev@jpoiret.xyz> (raw)
In-Reply-To: <87sfq6g96j.fsf@jpoiret.xyz>
* doc/guix.texi: Remove doubled Josselin Poiret copyright line.
---
doc/guix.texi | 1 -
1 file changed, 1 deletion(-)
diff --git a/doc/guix.texi b/doc/guix.texi
index 31f391357d..d9b26e440c 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -99,7 +99,6 @@ Copyright @copyright{} 2021 Alice Brenon@*
Copyright @copyright{} 2021, 2022 Josselin Poiret@*
Copyright @copyright{} 2021 Andrew Tropin@*
Copyright @copyright{} 2021 Sarah Morgensen@*
-Copyright @copyright{} 2021 Josselin Poiret@*
Copyright @copyright{} 2022 Remco van 't Veer@*
Copyright @copyright{} 2022 Aleksandr Vityazev@*
--
2.34.0
next prev parent reply other threads:[~2022-04-21 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 2:27 bug#54783: ZRAM default priority wrong Stefan Baums
2022-04-21 7:57 ` Josselin Poiret via Bug reports for GNU Guix
2022-04-21 8:06 ` Stefan Baums
2022-04-21 13:49 ` bug#54783: [PATCH 1/2] system: Align zram priority with swap-space spec to clarify Josselin Poiret via Bug reports for GNU Guix
2022-05-24 15:42 ` bug#54783: ZRAM default priority wrong Maxim Cournoyer
2022-05-24 17:16 ` bug#54783: [v2 0/2] Clarify zram priority Josselin Poiret via Bug reports for GNU Guix
2022-05-24 17:16 ` bug#54783: [PATCH v2 1/2] system: Align zram priority with swap-space spec to clarify Josselin Poiret via Bug reports for GNU Guix
2022-05-24 17:16 ` bug#54783: [PATCH v2 2/2] doc: Remove double copyright Josselin Poiret via Bug reports for GNU Guix
2022-04-21 13:49 ` Josselin Poiret via Bug reports for GNU Guix [this message]
2022-06-11 5:56 ` bug#54783: ZRAM default priority wrong Maxim Cournoyer
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=20220421134921.1505-2-dev@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=54783@debbugs.gnu.org \
--cc=baums@stefanbaums.com \
--cc=dev@jpoiret.xyz \
/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).