From: ludo@gnu.org (Ludovic Courtès)
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Consolidate libjpeg, libpng, and libtiff into one module
Date: Thu, 26 Jun 2014 14:42:23 +0200 [thread overview]
Message-ID: <87simru9jk.fsf@gnu.org> (raw)
In-Reply-To: <8738esv8eb.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> (David Thompson's message of "Wed, 25 Jun 2014 20:09:32 -0400")
David Thompson <dthompson2@worcester.edu> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> David Thompson <dthompson2@worcester.edu> skribis:
>>
>>> From 6298deeab6104b908a7356786ce09f395a32d7e3 Mon Sep 17 00:00:00 2001
>>> From: David Thompson <dthompson2@worcester.edu>
>>> Date: Wed, 25 Jun 2014 08:39:02 -0400
>>> Subject: [PATCH] gnu: Consolidate libjpeg, libpng, and libtiff into one
>>> module.
>>
>> Sounds like a good idea! Perhaps wait until Friday before applying it,
>> in case someone has anything to say.
>>
>
> Sure.
>
>>> * gnu/packages/image.scm: New file.
>>>
>>> * gnu-system.am (GNU_SYSTEM_MODULES): Add image.scm and remove libjpeg.scm,
>>> libpng.scm, and libtiff.scm.
>>
>> No blank lines for related changes, please.
>>
>
> Fixed.
>
>>> * gnu/packages/libjpeg.scm
>>> * gnu/packages/libpng.scm
>>> * gnu/packages/libtiff.scm: Delete files.
>>
>> Usually when listing several files it’s like this:
>>
>> * foo.scm, bar.scm, baz.scm: Frob.
>>
>> Could you make it that way?
>>
>
> Done.
>
> How does it look now?
Perfect, thanks. :-)
OK to push tomorrow (Friday) if nobody objects by then.
Ludo’.
next prev parent reply other threads:[~2014-06-26 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 12:47 [PATCH] gnu: Consolidate libjpeg, libpng, and libtiff into one module David Thompson
2014-06-25 13:07 ` David Thompson
2014-06-25 19:37 ` Ludovic Courtès
2014-06-26 0:09 ` David Thompson
2014-06-26 12:42 ` Ludovic Courtès [this message]
2014-06-27 10:33 ` David Thompson
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=87simru9jk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@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 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).