From: "Yaakov (Cygwin Ports)" <yselkowitz@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] giflib
Date: Fri, 14 Nov 2008 05:04:00 -0000 [thread overview]
Message-ID: <491D06AF.9010100@users.sourceforge.net> (raw)
In-Reply-To: <20081112104419.GI17719@calimero.vinschen.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Corinna Vinschen wrote:
> On Nov 11 11:38, Yaakov (Cygwin Ports) wrote:
>> I propose to add giflib to (mostly) replace libungif (which is currently
>> mine). The latter is no longer maintained because there are no
>> remaining legal impediments to using giflib.
>>
> Shoot.
Done.
Dr. Volker Zell: I changed the dependency of libming-devel from libungif
to libungif-devel.
Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkkdBq4ACgkQpiWmPGlmQSMpkgCdGsImcF9/sQiNZHx8XiFLH77N
D2QAoPGS+IyM4197cee9jV+BS/MKziLK
=ZrrY
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2008-11-14 5:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 17:40 Yaakov (Cygwin Ports)
2008-11-12 10:42 ` Corinna Vinschen
2008-11-14 5:04 ` Yaakov (Cygwin Ports) [this message]
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=491D06AF.9010100@users.sourceforge.net \
--to=yselkowitz@users.sourceforge.net \
--cc=cygwin-apps@cygwin.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).