public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: Lemures Lemniscati <lemures.lemniscati@gmail.com>
Cc: cygwin-apps@cygwin.com
Subject: Re: [ITA] libiconv-1.16-1, libiconv2-1.16, libcharset1-1.16-1
Date: Fri, 31 Jul 2020 04:38:29 +0900	[thread overview]
Message-ID: <20200731043826.781F.50F79699@gmail.com> (raw)
In-Reply-To: <20200718201825.237C.50F79699@gmail.com>

Date: Sat, 18 Jul 2020 20:18:27 +0900
From: Lemures Lemniscati

> Date: Sat, 18 Jul 2020 12:45:35 +0200
> From: Achim Gratz
> 
> > Lemures Lemniscati via Cygwin-apps writes:
> > > I've prepared it at a branch w_build-requires in the repository
> > > https://cygwin.com/git/cygwin-packages/libiconv.git .
> > >
> > > But not merged yet to master branch.
> > 
> > You should push experiments to the playground branch, which you can
> > force-push and delete without intervention from Jon.  You can check the
> > CI results here:
> > 
> > https://cygwin.com/cgi-bin2/jobs.cgi
> > https://ci.appveyor.com/project/cygwin/scallywag/history
> > 
> 
> Very wonderful!
> Thank you.

By the way, when should I promote libiconv-1.16-2 from test to current?

But, I don't know how to promote.
Should I rebuild and release as libiconv-1.16-3 ?

Regards,

Lem

  reply	other threads:[~2020-07-30 19:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11  2:03 Lemures Lemniscati
2020-07-11 17:45 ` Marco Atzeri
2020-07-11 22:01   ` Lemures Lemniscati
2020-07-18  8:29     ` Achim Gratz
2020-07-18 10:34       ` Lemures Lemniscati
2020-07-18 10:45         ` Achim Gratz
2020-07-18 11:18           ` Lemures Lemniscati
2020-07-30 19:38             ` Lemures Lemniscati [this message]
2020-07-31  4:22               ` Marco Atzeri
2020-08-01  4:18                 ` Lemures Lemniscati
2020-07-12 22:16   ` Yaakov Selkowitz

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=20200731043826.781F.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).