public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Rito via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,  Eric Sunshine <sunshine@sunshineco.com>,
	 Rito <rito@ritovision.com>
Subject: Re: [PATCH v2 0/5] gitweb: fix broken mobile layouts across views
Date: Fri, 20 Feb 2026 14:38:34 -0800	[thread overview]
Message-ID: <xmqqo6ljujkl.fsf@gitster.g> (raw)
In-Reply-To: <pull.2043.v2.git.1771257211.gitgitgadget@gmail.com> (Rito via GitGitGadget's message of "Mon, 16 Feb 2026 15:53:26 +0000")

"Rito via GitGitGadget" <gitgitgadget@gmail.com> writes:

> Summary
> =======
>
> This patch series fixes mobile responsiveness bugs that currently break page
> layouts in gitweb. The approach is adaptive rather than transformative:
> preserve legacy desktop layout, add targeted mobile constraints at ≤768, and
> prevent content from escaping its containers and breaking the layout.

The latest round of these patches have seen no reactions; is
everybody happy with them, or do we have too small number of people
who care about gitweb or feel competent enough in the area to review?

I am inclined to say that we should just merge it down and see who
screams.  Maybe we hear nothing, or complaints, or praises.


  parent reply	other threads:[~2026-02-20 22:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09 23:17 [PATCH 0/5] gitweb: fix broken mobile layouts across views Rito via GitGitGadget
2026-02-09 23:17 ` [PATCH 1/5] gitweb: add viewport meta tag for mobile devices Rito Rhymes via GitGitGadget
2026-02-09 23:17 ` [PATCH 2/5] gitweb: prevent project search bar from overflowing on mobile Rito Rhymes via GitGitGadget
2026-02-09 23:17 ` [PATCH 3/5] gitweb: fix mobile page overflow across log/commit/blob/diff views Rito Rhymes via GitGitGadget
2026-02-15 23:20   ` Eric Sunshine
2026-02-17 12:29     ` Matthew Pellerito
2026-02-09 23:17 ` [PATCH 4/5] gitweb: fix mobile footer overflow by wrapping text and clearing floats Rito Rhymes via GitGitGadget
2026-02-09 23:17 ` [PATCH 5/5] gitweb: let page header grow on mobile for long wrapped project names Rito Rhymes via GitGitGadget
2026-02-16 15:53 ` [PATCH v2 0/5] gitweb: fix broken mobile layouts across views Rito via GitGitGadget
2026-02-16 15:53   ` [PATCH v2 1/5] gitweb: add viewport meta tag for mobile devices Rito Rhymes via GitGitGadget
2026-02-16 15:53   ` [PATCH v2 2/5] gitweb: prevent project search bar from overflowing on mobile Rito Rhymes via GitGitGadget
2026-02-16 15:53   ` [PATCH v2 3/5] gitweb: fix mobile page overflow across log/commit/blob/diff views Rito Rhymes via GitGitGadget
2026-02-16 15:53   ` [PATCH v2 4/5] gitweb: fix mobile footer overflow by wrapping text and clearing floats Rito Rhymes via GitGitGadget
2026-02-16 15:53   ` [PATCH v2 5/5] gitweb: let page header grow on mobile for long wrapped project names Rito Rhymes via GitGitGadget
2026-02-20 22:38   ` Junio C Hamano [this message]
2026-02-21  0:17     ` [PATCH v2 0/5] gitweb: fix broken mobile layouts across views Rito Rhymes
2026-02-22  8:39     ` Eric Sunshine

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=xmqqo6ljujkl.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=rito@ritovision.com \
    --cc=sunshine@sunshineco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox