public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Than Ngo <than@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/chromium] epel9-next: fix typo
Date: Fri, 07 Aug 2026 16:05:10 GMT [thread overview]
Message-ID: <178611871009.1.2426575516595924844.rpms-chromium-0b9451b207df@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : 0b9451b207dfdff35685aa2c46866ef8e833d134
Author : Than Ngo <than@redhat.com>
Date : 2023-05-03T19:35:15+02:00
Stats : +1/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/0b9451b207dfdff35685aa2c46866ef8e833d134?branch=epel9-next
Log:
fix typo
---
diff --git a/chromium-113-workaround_clang_bug-structured_binding.patch b/chromium-113-workaround_clang_bug-structured_binding.patch
index 88ba646..2199ae4 100644
--- a/chromium-113-workaround_clang_bug-structured_binding.patch
+++ b/chromium-113-workaround_clang_bug-structured_binding.patch
@@ -24,7 +24,7 @@ diff -up chromium-113.0.5672.63/third_party/blink/renderer/core/layout/ng/grid/n
+ auto& workaround_clang_bug = sizing_tree->At(current_grid_index);
+ auto& grid_items = workaround_clang_bug.grid_items;
+ auto& layout_data = workaround_clang_bug.layout_data;
-+ auto& subtree_size = workaround_clang_bug.subtree_size
++ auto& subtree_size = workaround_clang_bug.subtree_size;
auto InitAndCacheTrackSizes = [&](GridTrackSizingDirection track_direction) {
InitializeTrackCollection(opt_subgrid_data, track_direction, &layout_data);
next reply other threads:[~2026-08-07 16:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 16:05 Than Ngo [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-07 16:08 [rpms/chromium] epel9-next: Fix typo Than Ngo
2026-08-07 16:08 Than Ngo
2026-08-07 16:07 Than Ngo
2026-08-07 16:07 [rpms/chromium] epel9-next: fix typo Than Ngo
2026-08-07 16:06 Than Ngo
2026-08-07 16:06 Than Ngo
2026-08-07 16:06 Than Ngo
2026-08-07 16:04 Than Ngo
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=178611871009.1.2426575516595924844.rpms-chromium-0b9451b207df@fedoraproject.org \
--to=than@redhat.com \
--cc=git-commits@fedoraproject.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