From: jgart via Guix-patches via <guix-patches@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 52505-done@debbugs.gnu.org, 52505@debbugs.gnu.org
Subject: [bug#52505] [PATCH 1/2] Guix Documentation Meetup Patches
Date: Wed, 2 Feb 2022 19:43:08 -0500 [thread overview]
Message-ID: <20220202194308.GC8620@gac.attlocal.net> (raw)
In-Reply-To: <87k0ekuso8.fsf@nicolasgoaziou.fr>
On Fri, 28 Jan 2022 10:16:07 +0100 Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> jgart via Guix-patches via <guix-patches@gnu.org> writes:
>
> > Here are two patches that we worked on.
>
> Applied v3. Thank you!
Thanks Nicolas!
much appreciated,
jgart
prev parent reply other threads:[~2022-02-03 0:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 11:16 [bug#52505] [PATCH 1/2] Guix Documentation Meetup Patches jgart via Guix-patches via
2021-12-15 11:20 ` [bug#52505] [PATCH 1/2] doc: Explain the use of make clean-go when an ABI mismatch occurs jgart via Guix-patches via
2021-12-15 11:20 ` [bug#52505] [PATCH 2/2] doc: Mention how to remedy "source file ... newer than compiled error" jgart via Guix-patches via
2021-12-15 12:39 ` zimoun
2021-12-15 13:14 ` Nicolas Goaziou
2021-12-15 13:08 ` [bug#52505] [PATCH 1/2] doc: Explain the use of make clean-go when an ABI mismatch occurs Nicolas Goaziou
2021-12-15 22:34 ` [bug#52505] [PATCH v2 " jgart via Guix-patches via
2021-12-15 22:34 ` [bug#52505] [PATCH v2 2/2] doc: Mention how to remedy "source file ... newer than compiled error" jgart via Guix-patches via
2021-12-16 6:46 ` [bug#52505] [PATCH v3 1/2] doc: Explain the use of make clean-go when an ABI mismatch occurs jgart via Guix-patches via
2021-12-16 6:46 ` [bug#52505] [PATCH v3 2/2] doc: Mention how to remedy "source file ... newer than compiled error" jgart via Guix-patches via
2022-01-28 9:16 ` bug#52505: [PATCH 1/2] Guix Documentation Meetup Patches Nicolas Goaziou
2022-02-03 0:43 ` jgart via Guix-patches via [this message]
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=20220202194308.GC8620@gac.attlocal.net \
--to=guix-patches@gnu.org \
--cc=52505-done@debbugs.gnu.org \
--cc=52505@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=mail@nicolasgoaziou.fr \
/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.