From: Marco Atzeri <marco.atzeri@gmail.com>
To: "Alois Schlögl" <alois.schloegl@gmail.com>, cygwin-apps@cygwin.com
Subject: Re: [ITP] biosig [was: Re: newcomer issues when packaging biosig, stimfit, etc.]
Date: Wed, 26 Jan 2022 05:52:28 +0100 [thread overview]
Message-ID: <9e3d8a31-5885-3569-466e-5acaa7093bee@gmail.com> (raw)
In-Reply-To: <23b42d82-65b3-66b4-dec5-b47a3efca04b@gmail.com>
On 26.01.2022 00:50, Alois Schlögl wrote:
>
>
> Hi Marco,
>
>
> thanks for the improvements (especially, libb64 which enables
> biosig_fhir, and python-biosig).
> Attached is a revised version. Check on playground was successful [1].
>
>
> Regards,
> Alois
>
>
> [1] https://github.com/cygwin/scallywag/actions/runs/1748211333
>
GTG for me.
I added the package on the package list
$ grep biosig cygwin-pkg-maint
biosig Alois Schloegl
you should be able to upload.
https://cygwin.com/package-upload.html
Regards
Marco
next prev parent reply other threads:[~2022-01-26 4:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <99eff890-3d7f-7fa9-1f42-d8d611b92ded@gmail.com>
2022-01-08 17:41 ` newcomer issues when packaging biosig,stimfit, etc Marco Atzeri
2022-01-08 19:15 ` Marco Atzeri
2022-01-08 19:24 ` Marco Atzeri
[not found] ` <a3f8e657-1e1d-c582-2a07-806c6c03be02@gmail.com>
2022-01-12 5:47 ` Marco Atzeri
2022-01-12 6:16 ` Brian Inglis
2022-01-12 22:59 ` [ITP] biosig [was: Re: newcomer issues when packaging biosig, stimfit, etc.] Alois Schlögl
2022-01-14 10:09 ` Marco Atzeri
2022-01-14 21:48 ` Alois Schlögl
2022-01-15 18:01 ` Marco Atzeri
2022-01-15 20:44 ` Achim Gratz
2022-01-17 21:44 ` Alois Schlögl
2022-01-18 5:32 ` Brian Inglis
2022-01-18 21:50 ` Alois Schlögl
2022-01-18 22:56 ` Brian Inglis
2022-01-19 3:51 ` Brian Inglis
2022-01-20 20:48 ` Alois Schlögl
2022-01-21 12:53 ` Jon Turney
2022-01-16 22:13 ` Alois Schlögl
2022-01-22 17:52 ` Marco Atzeri
2022-01-25 23:50 ` Alois Schlögl
2022-01-26 4:52 ` Marco Atzeri [this message]
2022-01-26 22:47 ` Marco Atzeri
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=9e3d8a31-5885-3569-466e-5acaa7093bee@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=alois.schloegl@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).