From: jgart via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Julien Lepiller <julien@lepiller.eu>,
53287@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#53287] (no subject)
Date: Tue, 25 Jan 2022 02:27:31 -0500 [thread overview]
Message-ID: <20220125022731.GB6597@gac.attlocal.net> (raw)
In-Reply-To: <20220115180847.31250-1-jgart@dismail.de>
Lepiller <julien@lepiller.eu>, Matt Trzcinski <matt@excalamus.com>,
Fabio Natali <me@fabionatali.com>, Gabor Boskovits <boskovits@gmail.com>
Bcc:
Subject: Re: bug#53287: [PATCH] doc: Document the documentation process.
Reply-To:
In-Reply-To: <87wnis3ijy.fsf_-_@gnu.org>
On Fri, 21 Jan 2022 22:06:25 +0100 Ludovic Courtès <ludo@gnu.org> wrote:
> Could you send an updated patch?
Hi Zimoun and Ludo,
Thank you for the reviews! It is much appreciated.
I'll get back to you soon regarding an updated patch. I'll probably be able to
work on this again this coming weekend once my time frees up.
If anyone from the meetup would like to send an updated patch before
then feel free to do so.
> Thumbs up to everyone who participated in this meetup!
Thank you! Much appreciated.
I'm looking to forward to more Guix hacking with everyone.
all best,
jgart
next prev parent reply other threads:[~2022-01-25 8:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 18:08 [bug#53287] [PATCH] doc: Document the documentation process jgart via Guix-patches via
2022-01-15 19:27 ` [bug#53287] [PATCH v2] " jgart via Guix-patches via
2022-01-15 19:45 ` [bug#53287] [PATCH v3] " jgart via Guix-patches via
2022-01-17 16:31 ` zimoun
2022-01-21 21:06 ` [bug#53287] [PATCH] " Ludovic Courtès
2022-01-25 7:27 ` jgart via Guix-patches via [this message]
2022-04-08 18:26 ` Luis Felipe via Guix-patches via
2022-07-07 18:42 ` Maxim Cournoyer
2022-07-07 21:41 ` Luis Felipe via Guix-patches via
2022-07-07 23:55 ` jgart via Guix-patches via
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=20220125022731.GB6597@gac.attlocal.net \
--to=guix-patches@gnu.org \
--cc=53287@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=julien@lepiller.eu \
--cc=ludo@gnu.org \
--cc=zimon.toutoune@gmail.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.
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.