From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: K Jayatheerth <jayatheerthkulkarni2005@gmail.com>
Subject: Re: [PATCH v8 0/2] Avoid submodule overwritten and skip redundant active entries
Date: Mon, 07 Jul 2025 15:34:03 -0700 [thread overview]
Message-ID: <xmqq4ivn3a1w.fsf@gitster.g> (raw)
In-Reply-To: <20250608032705.11990-1-jayatheerthkulkarni2005@gmail.com> (K. Jayatheerth's message of "Sun, 8 Jun 2025 08:57:03 +0530")
K Jayatheerth <jayatheerthkulkarni2005@gmail.com> writes:
> The first patch i.e. prevent overwriting .gitmodules entry on path reuse
> is exactly the same
>
> The second patch however i.e.
> skip redundant active entries when pattern covers path
> has changed logic
> with the helper function being code maintainance because
> of the duplicated logic. I've tried to wrap it as much as
> possible to it's own core need without having to change it
> unless the core way of submodules addition and active status
> itself changes.
>
> The CI was tested in which
> the only compiler error I found was
> osx-gcc
> Which I suppose is already addressed,
> apart from this all of the other tests
> ran successfully which includes the
> t7413 (prvious 9) and the new one.
>
>
> K Jayatheerth (2):
> submodule: prevent overwriting .gitmodules entry on path reuse
> submodule: skip redundant active entries when pattern covers path
Haven't seen any comment from others on this topic for quite a
while. How does this one look to those who do use submodules (I am
not one of them)?
Thanks.
prev parent reply other threads:[~2025-07-07 22:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-24 7:36 [PATCH v7 0/2] Avoid submodule overwritten and skip redundant active entries K Jayatheerth
2025-05-24 7:36 ` [PATCH v7 1/2] submodule: prevent overwriting .gitmodules entry on path reuse K Jayatheerth
2025-05-27 14:01 ` Junio C Hamano
2025-05-24 7:36 ` [PATCH v7 2/2] submodule: skip redundant active entries when pattern covers path K Jayatheerth
2025-05-27 14:42 ` Junio C Hamano
2025-05-29 4:23 ` JAYATHEERTH K
2025-06-04 4:22 ` Junio C Hamano
2025-06-06 14:41 ` JAYATHEERTH K
2025-06-08 3:27 ` [PATCH v8 0/2] Avoid submodule overwritten and skip redundant active entries K Jayatheerth
2025-06-08 3:27 ` [PATCH v8 1/2] submodule: prevent overwriting .gitmodules entry on path reuse K Jayatheerth
2025-07-09 2:50 ` D. Ben Knoble
2025-07-20 12:25 ` JAYATHEERTH K
2025-07-25 17:28 ` Ben Knoble
2025-06-08 3:27 ` [PATCH v8 2/2] submodule: skip redundant active entries when pattern covers path K Jayatheerth
2025-07-09 2:50 ` D. Ben Knoble
2025-07-09 14:52 ` Junio C Hamano
2025-07-17 16:58 ` Junio C Hamano
2025-07-18 14:24 ` JAYATHEERTH K
2025-07-07 22:34 ` Junio C Hamano [this message]
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=xmqq4ivn3a1w.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jayatheerthkulkarni2005@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.