From: zimoun <zimon.toutoune@gmail.com>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: "39635@debbugs.gnu.org" <39635@debbugs.gnu.org>,
sirgazil <sirgazil@zoho.com>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#39635] [PATCH] website: Modify use of H1 headings
Date: Tue, 18 Oct 2022 17:58:20 +0200 [thread overview]
Message-ID: <86zgdtxgwz.fsf_-_@gmail.com> (raw)
In-Reply-To: <Ye8Qtu3z3EJLQkPYTko-BBX7xEEqR9sL9a6Blwe7HQFgLe2jc1973WZzO7WnfovRVLt9Oky1wdss6YmT-YcaGytjgN8uRlVD7bStoRf10is=@protonmail.com> (Luis Felipe's message of "Sat, 10 Oct 2020 19:51:02 +0000")
Hi Luis,
Sorry for not being super responsive. It is about an old patch#39635
submission [1].
1: <http://issues.guix.gnu.org/issue/39635>
On Sat, 10 Oct 2020 at 19:51, Luis Felipe <luis.felipe.la@protonmail.com> wrote:
> On Friday, October 9, 2020 2:49 AM, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>> Thanks for the patch! It makes sense. Unfortunately it doesn't apply
>> with 'git am' :-/. Could you rebase it on the current master branch of
>> guix-artwork?
[...]
> I'd redo the work, and send a new patch, but I haven't had much luck with my
> patches for the website, so I guess I pass for now.
What is the status? Do we close this submission? Are we waiting for an
update? Maybe it is included by another patch.
Cheers,
simon
next prev parent reply other threads:[~2022-10-18 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 18:26 [bug#39635] [PATCH] website: Modify use of H1 headings sirgazil via Guix-patches via
2020-10-06 14:03 ` [bug#39635] " Luis Felipe via Guix-patches via
2020-10-09 2:49 ` [bug#39635] [PATCH] " Maxim Cournoyer
2020-10-10 19:51 ` Luis Felipe via Guix-patches via
2020-10-12 8:02 ` zimoun
2020-10-12 14:08 ` Luis Felipe via Guix-patches via
2020-10-13 1:36 ` Maxim Cournoyer
2022-10-18 15:58 ` zimoun [this message]
2022-10-18 21:34 ` Luis Felipe 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86zgdtxgwz.fsf_-_@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=39635@debbugs.gnu.org \
--cc=luis.felipe.la@protonmail.com \
--cc=maxim.cournoyer@gmail.com \
--cc=sirgazil@zoho.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).