From: Giovanni Biscuolo <g@xelera.eu>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 69783@debbugs.gnu.org, Luis Felipe <sirgazil@zoho.com>
Subject: [bug#69783] [PATCH] doc: build: Update paths to style sheets.
Date: Sun, 17 Mar 2024 11:51:19 +0100 [thread overview]
Message-ID: <875xxlrv14.fsf@xelera.eu> (raw)
In-Reply-To: <877ci2ph5v.fsf@pelzflorian.de>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
Hello Florian,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
> Reopen.
> I had not closed yet because I still had a request to the maintainers:
>
> https://lists.gnu.org/archive/html/guix-patches/2024-03/msg01035.html
Uh sorry! I missed it.
But then, why not wait for the missing information and related patch and
commit all the patches in this bug as a coherent patchset "in bulk"? If
needed "we" could use a dedicated "doc" branch to test this, no?
I understand that this patch series is "just" for doc presentation
(style) and the missing patch(es) do not "hard" break the manual, but
this workflow makes harder for casual contributors like me to help in
"bug gardening".
WDYT?
Sorry again for the confusion.
Happy hacking! Gio'
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2024-03-17 10:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 20:44 [bug#69783] [PATCH]: website: Convert old style sheets into a theme Luis Felipe via Guix-patches via
2024-03-14 16:56 ` pelzflorian (Florian Pelz)
2024-03-14 20:16 ` Luis Felipe via Guix-patches via
2024-03-15 10:19 ` pelzflorian (Florian Pelz)
2024-03-15 15:33 ` [bug#69783] [PATCH v2] " sirgazil--- via Guix-patches via
2024-03-15 22:51 ` pelzflorian (Florian Pelz)
2024-03-15 19:34 ` [bug#69783] [PATCH] doc: build: Update paths to style sheets sirgazil--- via Guix-patches via
2024-03-16 9:34 ` bug#69783: " Giovanni Biscuolo
2024-03-16 11:09 ` [bug#69783] " pelzflorian (Florian Pelz)
2024-03-16 13:52 ` Luis Felipe via Guix-patches via
2024-03-16 17:47 ` pelzflorian (Florian Pelz)
2024-03-17 10:51 ` Giovanni Biscuolo [this message]
2024-03-17 16:52 ` pelzflorian (Florian Pelz)
2024-03-17 17:57 ` pelzflorian (Florian Pelz)
2024-03-17 20:21 ` [bug#69783] [PATCH] hydra: nginx: Adjust to website themes in guix-artwork Florian Pelz
2024-03-24 18:19 ` [bug#69783] [PATCH v2 1/2] hydra: nginx: Redirect 1.4.0 manual resources due to themes move Florian Pelz
2024-03-30 14:28 ` Ludovic Courtès
2024-03-24 18:19 ` [bug#69783] [PATCH v2 2/2] hydra: nginx: Further adjust to website themes in guix-artwork Florian Pelz
2024-03-30 11:00 ` Ludovic Courtès
2024-03-31 10:07 ` bug#69783: " pelzflorian (Florian Pelz)
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=875xxlrv14.fsf@xelera.eu \
--to=g@xelera.eu \
--cc=69783@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
--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).