From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: 49213@debbugs.gnu.org
Subject: [bug#49213] (no subject)
Date: Wed, 30 Jun 2021 22:20:06 +0200 [thread overview]
Message-ID: <610a5483-6387-e66b-f476-e3ed89de2643@web.de> (raw)
In-Reply-To: <2d217a4c-13c3-6bbd-cbd4-1b156d16d911@raghavgururajan.name>
On 30.06.21 22:16, Raghav Gururajan via Guix-patches via wrote:
> Hi Maixme!
>
>> One day seems a lot less than two weeks, and I haven't seen
>> a reply. Did I miss any replies, or was it ‘replied’ to on IRC,
>> or ...?
>
> Sorry about that. I was interacting with Tobias in IRC about this patch
> that day (https://logs.guix.gnu.org/guix/2021-06-25.log). After some
> corrections, I was confident about that the patch with testing and I
> pushed it. That said. I'll leave the future threads for more time
> despite discussing on IRC. :)
In that case I think its not really necessary to leave the patch longer
on the mailing list. Instead you could add something like "reviewed
together with XY in IRC" on your closing email :)
next prev parent reply other threads:[~2021-06-30 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 18:51 [bug#49213] [PATCH v1] services: certbot: Add option to use CSR file Raghav Gururajan via Guix-patches via
2021-06-24 19:18 ` [bug#49213] [PATCH v2] " Raghav Gururajan via Guix-patches via
2021-06-24 21:58 ` [bug#49213] [PATCH v3] " Raghav Gururajan via Guix-patches via
2021-06-24 21:59 ` [bug#49213] [PATCH v4] " Raghav Gururajan via Guix-patches via
2021-06-24 22:20 ` [bug#49213] [PATCH v5] " Raghav Gururajan via Guix-patches via
2021-06-24 22:39 ` bug#49213: (no subject) Raghav Gururajan via Guix-patches via
2021-06-30 19:56 ` [bug#49213] " Maxime Devos
2021-06-30 20:16 ` Raghav Gururajan via Guix-patches via
2021-06-30 20:20 ` Jonathan Brielmaier [this message]
2021-07-01 8:05 ` Maxime Devos
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=610a5483-6387-e66b-f476-e3ed89de2643@web.de \
--to=jonathan.brielmaier@web.de \
--cc=49213@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.