From: Andreas Enge <andreas@enge.fr>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org, Rutger Helling <rhelling@mykolab.com>
Subject: Re: Moving packages over to new module
Date: Thu, 22 Feb 2018 11:43:51 +0100 [thread overview]
Message-ID: <20180222104351.GA3969@jurong> (raw)
In-Reply-To: <877er5qrd9.fsf@elephly.net>
On Thu, Feb 22, 2018 at 10:57:06AM +0100, Ricardo Wurmus wrote:
> We need to move the copyright notices as well. For that I usually look
> at the git log for the packages that should be moved. Since we’re using
> predictable commit messages this can easily be grep’ed from the git log.
This would require to also look at all the other packages in the module,
to decide whether the copyright notice should be moved or copied.
Maybe "git blame MODULE.scm" could also be helpful in that respect:
If used after the packages have been moved, it shows who has contributed
to the remaining packages.
Andreas
next prev parent reply other threads:[~2018-02-22 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 9:29 Moving packages over to new module Rutger Helling
2018-02-22 9:51 ` ng0
2018-02-22 9:57 ` Ricardo Wurmus
2018-02-22 10:43 ` Andreas Enge [this message]
2018-02-22 11:33 ` Rutger Helling
2018-02-22 11:51 ` Andreas Enge
2018-02-22 12:59 ` Rutger Helling
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=20180222104351.GA3969@jurong \
--to=andreas@enge.fr \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
--cc=rhelling@mykolab.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.
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).