From: Jelle Licht <jlicht@fsfe.org>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>, 62375@debbugs.gnu.org
Subject: [bug#62375] [PATCH 0/1] npm binary importer
Date: Tue, 02 Apr 2024 16:16:53 +0200 [thread overview]
Message-ID: <87o7arg88a.fsf@fsfe.org> (raw)
In-Reply-To: <ea36dc83-ad86-4da8-57d7-adf8630daeab@web.de>
Jonathan Brielmaier via Guix-patches via <guix-patches@gnu.org> writes:
> Hi Jelle,
>
> one rather unimportant remark. The commit message mentions Lars-Dominik
> as co-author:
> https://issues.guix.gnu.org/62375#12-lineno8
>
> But there is no copyright header for him in any of the added files...
Thanks for the reminder; it was a contribution that they shared in 2021,
so I've now added the copyright header in V4.
- Jelle
next prev parent reply other threads:[~2024-04-02 14:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 11:25 [bug#62375] [PATCH 0/1] npm binary importer jlicht
2023-03-22 11:27 ` [bug#62375] [PATCH] import: Add binary npm importer jlicht
2023-03-28 15:49 ` Ludovic Courtès
2023-04-08 18:29 ` Jelle Licht
2023-04-17 21:14 ` [bug#62375] [PATCH 0/1] npm binary importer Ludovic Courtès
2023-06-18 21:03 ` Ludovic Courtès
2023-06-22 9:39 ` Jelle Licht
2024-02-08 0:59 ` Nicolas Graves via Guix-patches via
2024-03-24 14:54 ` [bug#62375] Continue the npm-binary importer Pablo Zamora
2024-03-31 19:57 ` Jelle Licht
2024-03-31 22:03 ` Pablo Zamora
2024-03-31 19:46 ` [bug#62375] [PATCH v2] import: Add binary npm importer jlicht
2024-03-31 20:37 ` [bug#62375] [PATCH v3] " jlicht
2024-04-01 20:41 ` Ludovic Courtès
2024-04-02 14:12 ` Jelle Licht
2024-04-01 22:01 ` [bug#62375] [PATCH 0/1] npm binary importer Jonathan Brielmaier via Guix-patches via
2024-04-02 14:16 ` Jelle Licht [this message]
2024-04-02 14:13 ` [bug#62375] [PATCH v4] import: Add binary npm importer jlicht
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=87o7arg88a.fsf@fsfe.org \
--to=jlicht@fsfe.org \
--cc=62375@debbugs.gnu.org \
--cc=jonathan.brielmaier@web.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.