all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: Guix-devel <Guix-devel@gnu.org>
Subject: Re: [PATCH 1/2] gnu: glibc/linux: Rename "linux-headers" input to "kernel-headers".
Date: Fri, 28 Aug 2015 11:30:24 +0200	[thread overview]
Message-ID: <87k2sfu5e7.fsf@gnu.org> (raw)
In-Reply-To: <CAFtzXzMf2L-t_VJ+MuRjW+6ONZv4=zL7Ow71+kYT6Z6VK_K=CA@mail.gmail.com> (Manolis Ragkousis's message of "Fri, 14 Aug 2015 17:29:40 +0300")

Manolis Ragkousis <manolis837@gmail.com> skribis:

> From f9759a80030e11dfb8257f2334d5ce8f5d009cc7 Mon Sep 17 00:00:00 2001
> From: Manolis Ragkousis <manolis837@gmail.com>
> Date: Fri, 14 Aug 2015 14:00:16 +0300
> Subject: [PATCH 1/2] gnu: glibc/linux: Rename "linux-headers" input to
>  "kernel-headers".

The subject should be more:

  gnu: glibc/linux: Change label from "linux-headers" to "kernel-headers".

because the package name itself is unchanged.

> * gnu/packages/base.scm (glibc/linux)[propagated-inputs]: Rename to "kernel-headers".
>   (glibc/hurd)[arguments]: Adjust accordingly.

A grep for ‘"linux-headers"’ in master shows that there are 4 files
matching.  These probably need to be updated as well?

Also, could we make this change on top of current master and apply it to
‘core-updates’?  I suppose that means ‘wip-hurd’ would need to be
rebased and adjusted, but despite this annoyance, that would probably
facilitate merging.

WDYT?

Thanks,
Ludo’.

  parent reply	other threads:[~2015-08-28  9:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14 14:29 [PATCH 1/2] gnu: glibc/linux: Rename "linux-headers" input to "kernel-headers" Manolis Ragkousis
2015-08-23 10:22 ` Manolis Ragkousis
2015-08-28  9:30 ` Ludovic Courtès [this message]
2015-08-28  9:34   ` Manolis Ragkousis
2015-09-07 11:20     ` Manolis Ragkousis
2015-09-22 12:47       ` Ludovic Courtès

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=87k2sfu5e7.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=Guix-devel@gnu.org \
    --cc=manolis837@gmail.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.