From: Dan Callaghan <djc@djc.id.au>
To: Iain Parris <ipv2.lst@parris.org>
Cc: supmua <supmua@googlegroups.com>, Gaute Hope <eg@gaute.vetsj.com>
Subject: Re: sup is up
Date: Tue, 16 Jun 2020 17:31:49 +1000 [thread overview]
Message-ID: <1592292621-sup-7396@sage.djc.id.au> (raw)
In-Reply-To: <1592168780-sup-6450@ceres>
Excerpts from Iain Parris's message of 2020-06-14 23:08:31 +01:00:
> Dan, Gaute - I hope I have accurately summarised our conversations.
> Would you like to add anything? :-)
Nothing to add, other than a big thanks to you Iain for kicking off this
process, and I look forward to publishing a new sup release with lots of
good fixes soon.
--
Dan Callaghan <djc@djc.id.au>
next prev parent reply other threads:[~2020-06-16 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 22:08 Iain Parris
2020-06-15 6:57 ` Gaute Hope
2020-06-16 7:31 ` Dan Callaghan [this message]
2020-06-21 8:51 ` [sup] " Matthieu Rakotojaona
2020-06-21 12:48 ` Iain Parris
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=1592292621-sup-7396@sage.djc.id.au \
--to=djc@djc.id.au \
--cc=eg@gaute.vetsj.com \
--cc=ipv2.lst@parris.org \
--cc=supmua@googlegroups.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