public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] perl-WWW-Curl
Date: Mon, 13 Apr 2015 20:51:00 -0000	[thread overview]
Message-ID: <552C2C28.1040004@gmail.com> (raw)
In-Reply-To: <87h9sj3irr.fsf@Rainer.invalid>

On 4/13/2015 9:55 PM, Achim Gratz wrote:
> Achim Gratz writes:
>> As requested here:
>>
>> https://cygwin.com/ml/cygwin/2015-03/msg00525.html
>>
>> The package provides a Perl binding to libcurl.  It compiles cleanly on
>> x86 and with an implicit conversion overflow warning on x86_64 (looks
>> harmless) and tests cleanly on both architectures.
>
> Ping…
>
>
> Regards,
> Achim.
>

I think you don't need any ITP for perl packages.
They are yours by default.

Do you need just an entry on
https://cygwin.com/cygwin-pkg-maint

?

Marco

  reply	other threads:[~2015-04-13 20:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 19:31 Achim Gratz
2015-04-13 19:55 ` Achim Gratz
2015-04-13 20:51   ` Marco Atzeri [this message]
2015-04-13 21:08     ` Marco Atzeri
2015-04-14 18:51     ` Achim Gratz

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=552C2C28.1040004@gmail.com \
    --to=marco.atzeri@gmail.com \
    --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).