all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rutger Helling <rhelling@mykolab.com>
To: Andreas Enge <andreas@enge.fr>
Cc: help-guix@gnu.org
Subject: Re: Moving packages over to new module
Date: Thu, 22 Feb 2018 12:33:22 +0100	[thread overview]
Message-ID: <20180222123322.3c2a5a04@mykolab.com> (raw)
In-Reply-To: <20180222104351.GA3969@jurong>

[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]

I ended up using git log --grep=.... and have moved the packages. Using
'git blame' I found that a few copyright lines can be removed from
games.scm now. If a person has only imported a module ((gnu packages
base) for example), should I keep the copyright notice or lose it?

On Thu, 22 Feb 2018 11:43:51 +0100
Andreas Enge <andreas@enge.fr> wrote:

> 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
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-02-22 11:33 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
2018-02-22 11:33     ` Rutger Helling [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180222123322.3c2a5a04@mykolab.com \
    --to=rhelling@mykolab.com \
    --cc=andreas@enge.fr \
    --cc=help-guix@gnu.org \
    /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.