From: Tom Tromey <tom@tromey.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH htdocs 1/2] css: start a file to hold common content
Date: Fri, 20 Oct 2023 11:11:26 -0600 [thread overview]
Message-ID: <87wmvhp6bl.fsf@tromey.com> (raw)
In-Reply-To: <ZS0Mo02c0/TSx7tv@vapier> (Mike Frysinger's message of "Mon, 16 Oct 2023 15:57:51 +0545")
>>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
Mike> should i take silence on the matter of CSS to mean that no one really
Mike> cares that much about how these are managed, and i should go ahead and
Mike> merge these improvements ?
I don't really know anything about how the web pages are handled.
Maybe Joel does? CCing him.
Tom
next prev parent reply other threads:[~2023-10-20 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 4:47 Mike Frysinger
2023-01-12 4:47 ` [PATCH htdocs 2/2] css: add dark mode support Mike Frysinger
2023-10-16 10:12 ` [PATCH htdocs 1/2] css: start a file to hold common content Mike Frysinger
2023-10-20 17:11 ` Tom Tromey [this message]
2023-11-29 8:05 ` Mike Frysinger
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=87wmvhp6bl.fsf@tromey.com \
--to=tom@tromey.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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.
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).