public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] libuninameslist-20200413-1, python-libuninameslist-0.2-1
Date: Sun, 02 Aug 2020 19:32:52 +0900	[thread overview]
Message-ID: <20200802193250.F398.50F79699@gmail.com> (raw)
In-Reply-To: <2003ea3a-e4f8-35ba-8189-77af6f1e32af@gmail.com>


Date: Sun, 2 Aug 2020 08:10:19 +0200
From: Marco Atzeri via Cygwin-apps <cygwin-apps@cygwin.com>

> On 01.08.2020 05:08, Lemures Lemniscati via Cygwin-apps wrote:
> > Date: Fri, 10 Jul 2020 19:19:01 +0900
> > From: Lemures Lemniscati
> > 
> >
> > Since there seems to be no demand for python-libuninameslist-*,
> > I've removed it and refreshed libuninameslist.cygport
> > to just update the library.
> 
> for what I see also Debian has not such package
> 
> > The new cygport file is forked here
> >    https://github.com/cygwin-lem/libuninameslist-cygport/tree/w_20200413p3
> > from http://cygwin.com/git/cygwin-packages/libuninameslist .
> >
> > Updated test package files are here as before:
> >    https://cygwin-lem.github.io/libuninameslist-cygport/
> >
> > ========
> > * Note:
> >
> > This library is to be linked from fontforge.
> >
> > Please, review it for ITA, again.
> >
> >
> > Regards,
> >
> > Lem
> > 
> one question, any reason to not use the 20200413 but going to the last source code ?
> 

Not so much reason :). Just because it is the latest and stable.
But LICENSE was slightly refined in its expressions.

> for the rest GTG, you can upload
> 
Thank you for reviewing, Marco.

Regards,

Lem

      reply	other threads:[~2020-08-02 10:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 15:30 Lemures Lemniscati
2020-07-09 12:13 ` Lemures Lemniscati
2020-07-09 18:46   ` Marco Atzeri
2020-07-10 10:19     ` Lemures Lemniscati
2020-08-01  3:08       ` Lemures Lemniscati
2020-08-02  6:10         ` Marco Atzeri
2020-08-02 10:32           ` Lemures Lemniscati [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=20200802193250.F398.50F79699@gmail.com \
    --to=lemures.lemniscati@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).