From: Junio C Hamano <gitster@pobox.com>
To: Zakariyah Ali <zakariyahali100@gmail.com>
Cc: git@vger.kernel.org, karthik.188@gmail.com,
Tian Yuchen <cat@malon.dev>
Subject: Re: [PATCH v5] t2000: modernize overall structure and path checks
Date: Tue, 07 Apr 2026 07:29:30 -0700 [thread overview]
Message-ID: <xmqqmrze7sj9.fsf@gitster.g> (raw)
In-Reply-To: <20260407034446.409175-1-zakariyahali100@gmail.com> (Zakariyah Ali's message of "Tue, 7 Apr 2026 04:44:46 +0100")
Zakariyah Ali <zakariyahali100@gmail.com> writes:
> This test script that dates back to 2005 certainly shows its age and
> both its style and the way the tests are laid out do not match the
> modern standard. Modernize it to match the current testing standards:
> ...
How does this relate to d8e34f97 (t2000: modernise overall
structure, 2026-03-28) that was merged to 'next' at 279c41a3 (Merge
branch 'za/t2000-modernise' into next, 2026-03-31) and is now in
'master' at 0713d3b7 (Merge branch 'za/t2000-modernise', 2026-04-06)?
The topioc appeared first in the issue 2026/03 #12 of the "What's
cooking" report (Mar 30th), marked for 'next'. Then the issue
2026/04 #01 of the report (Apr 1st) listed the topic in 'next'
slated for 'master'. The issue 2026/03 #02 (Apr 6th) reports it is
now in 'master'.
The description of this v5 patch looks suspiciously similar, as its
patch text, so I suspect it won't apply to my tree.
next prev parent reply other threads:[~2026-04-07 14:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 0:15 Github Patch Zakariyah Ali
2026-03-26 0:54 ` Pablo
2026-03-26 19:26 ` [GSoC PATCH v2] t2000: modernize path checks with test_path_is_* helpers Zakariyah Ali
2026-03-26 20:29 ` Junio C Hamano
2026-03-27 23:40 ` [GSoC][PATCH v3] t2000: modernise overall structure Zakariyah Ali
2026-03-30 12:31 ` Zakariyah Ali
2026-04-01 17:09 ` Tian Yuchen
2026-04-05 1:11 ` [PATCH v4 1/1] t2000: modernize overall structure and path checks Zakariyah Ali
2026-04-05 22:04 ` Karthik Nayak
2026-04-06 17:36 ` Tian Yuchen
2026-04-07 3:44 ` [PATCH v5] " Zakariyah Ali
2026-04-07 14:29 ` Junio C Hamano [this message]
2026-04-07 16:10 ` Junio C Hamano
2026-04-29 10:36 ` [PATCH v6] t2000: consolidate second scenario into a single test block Zakariyah Ali
2026-05-05 6:42 ` Zakariyah Ali
2026-05-12 6:15 ` Junio C Hamano
2026-05-12 20:01 ` [PATCH v6] t2000: consolidate second scenario into a single test Zakariyah Ali
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=xmqqmrze7sj9.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=cat@malon.dev \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=zakariyahali100@gmail.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.