From: "Rito Rhymes" <rito@ritovision.com>
To: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
"Rito Rhymes" <rito@ritovision.com>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
<git@vger.kernel.org>
Subject: Re: GitGitGadget's website is responsive, how about kernel.org?
Date: Fri, 13 Mar 2026 09:56:04 -0400 [thread overview]
Message-ID: <DH1PFQMH1ARY.3M5EECQAPU95@ritovision.com> (raw)
In-Reply-To: <20260313-adventurous-lemon-unicorn-278ccc@lemur>
Yikes! I'll have to take a look at that.
I just sent the first patch series.
I also have a follow-up patch ready that adds a clean mobile nav header
to complete the UI, if the first series merges.
next prev parent reply other threads:[~2026-03-13 13:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 6:52 GitGitGadget's website is responsive, how about kernel.org? Johannes Schindelin
2026-03-13 13:04 ` Konstantin Ryabitsev
2026-03-13 13:14 ` Rito Rhymes
2026-03-13 13:16 ` Konstantin Ryabitsev
2026-03-13 13:56 ` Rito Rhymes [this message]
2026-03-13 15:58 ` Junio C Hamano
2026-03-14 6:20 ` Rito Rhymes
2026-03-14 16:48 ` Junio C Hamano
2026-03-14 18:54 ` Rito Rhymes
2026-03-16 14:58 ` Konstantin Ryabitsev
2026-03-16 17:14 ` Rito Rhymes
2026-03-14 7:59 ` [PATCH v1 0/6] Allow site layouts to render properly on mobile devices Rito Rhymes
2026-03-14 7:59 ` [PATCH v1 1/6] add viewport meta tag for proper mobile rendering Rito Rhymes
2026-03-14 7:59 ` [PATCH v1 2/6] prevent wrapped headings from overlapping with text above it Rito Rhymes
2026-03-14 7:59 ` [PATCH v1 3/6] add 848px mobile banner adjustments to prevent overflow Rito Rhymes
2026-03-14 7:59 ` [PATCH v1 4/6] add responsive extras and footer layout adjustments to contain overflow Rito Rhymes
2026-03-14 7:59 ` [PATCH v1 5/6] contain horizontal overflow in core content and homepage releases layout Rito Rhymes
2026-03-14 7:59 ` [PATCH v1 6/6] improve mobile rendering of docutils tables Rito Rhymes
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=DH1PFQMH1ARY.3M5EECQAPU95@ritovision.com \
--to=rito@ritovision.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=konstantin@linuxfoundation.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