All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Rito Rhymes" <rito@ritovision.com>
Cc: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
	 "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	 <git@vger.kernel.org>
Subject: Re: GitGitGadget's website is responsive, how about kernel.org?
Date: Sat, 14 Mar 2026 09:48:50 -0700	[thread overview]
Message-ID: <xmqqv7eywe4t.fsf@gitster.g> (raw)
In-Reply-To: <DH2ADSKXNCXG.2DM7T0NF5NH59@ritovision.com> (Rito Rhymes's message of "Sat, 14 Mar 2026 02:20:55 -0400")

"Rito Rhymes" <rito@ritovision.com> writes:

> Actually...
>
> now that I've had time to think about it (and get some
> rest), I think it's best to keep the patch series review and
> discussion all in this thread, publicly and transparently.
>
> I initially defaulted to sending it separately to Konstantin directly
> because this is Git's archive, and I wanted to respect convention by
> keeping the thread appropriately scoped. At first, this seemed more like
> just a routing touchpoint.
>
> But seeing as there is no public mailing list for kernel.org's repo
> specifically, and this is basically already a sidecar thread about the
> site theme patch, we might as well consolidate the process here for
> simplicity and transparency. Plus, I imagine the site matters to most
> people in Git, and the mailing list is archived on lore.kernel.org
> anyway...
>
> This will allow anyone to review the code and comment on it.
>
> I'm sending the patch series again directly in this thread, and I
> think we should keep communication contained here (unless someone has
> a better idea).

I would not object discussion here, and I personally do not mind
having to see, and possibly ignore, more patches on this list, but
to those who come here to work with and work on Git, I am reasonably
sure that it will look offtopic to discuss how the k.org website
appears and behaves, and/or how a better version of it would appear
and behave.

I'll leave Konstantin with the final say.  I hope there are better
places, even though I do not now where they are as I do not do
websites.  I've seen folks with accounts at k.org discuss things on
mailing lists that is more limited for kernel.org users.

  reply	other threads:[~2026-03-14 16:48 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
2026-03-13 15:58       ` Junio C Hamano
2026-03-14  6:20         ` Rito Rhymes
2026-03-14 16:48           ` Junio C Hamano [this message]
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=xmqqv7eywe4t.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=rito@ritovision.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.
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.