From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
Alois Schloegl <alois.schloegl@gmail.com>
Subject: Re: [ITP] biosig [was: Re: newcomer issues when packaging biosig, stimfit, etc.]
Date: Fri, 21 Jan 2022 12:53:18 +0000 [thread overview]
Message-ID: <92ad1c03-03d0-8880-94e6-0f0b1f540ad1@dronecode.org.uk> (raw)
In-Reply-To: <b4945e21-20b7-c5e7-33ad-1f8fb2ad8ff7@gmail.com>
On 20/01/2022 20:48, Alois Schlögl wrote:
>
> In order to use the playgroun, I guess I need to provide my ssh key.
> Here it is:
>
> Name: Alois Schloegl
> ---- BEGIN SSH2 PUBLIC KEY ----
> AAAAC3NzaC1lZDI1NTE5AAAAILKBmNf1QN3lStTwpn46QIip7sS6zNKy0rG8WCYHv/ZU
> ---- END SSH2 PUBLIC KEY ----
Done.
> Updating ssh key for Alois Schloegl
> Fingerprint: 256 SHA256:bvMkxeY5KcLLESayAW43ZPOiYI9owtf0UKKWIWmue00 no comment (ED25519)
next prev parent reply other threads:[~2022-01-21 12:53 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 [this message]
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
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=92ad1c03-03d0-8880-94e6-0f0b1f540ad1@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).