On 8/29/25 5:03 PM, Junio C Hamano wrote:
Junio C Hamano <gitster@xxxxxxxxx> writes:
Elijah Newren <newren@xxxxxxxxx> writes:
On Thu, Aug 28, 2025 at 4:22 PM Junio C Hamano <gitster@xxxxxxxxx> wrote:
This seems to have a few comments that haven't been responded to
(plus a "This step looks good to me" or two). Can we get it unstuck
soonish? The topic is from mid July and I do not like to hold topics
in 'seen' for longer than a month without any activity.
Stolee built this series on top of Ayush's topic to avoid conflicts
for you, and he said
(https://lore.kernel.org/git/c3c0fbef-f395-4972-8352-dd89af6799d5@xxxxxxxxx/)
that since you marked this as blocking on Ayush's topic, he didn't
want to update until that topic moved.
Do you want to instead kick Ayush's topic out and have Stolee rebase
to no longer be on top of Ayush's, and have Ayush rebase anything he
might do on top of Stolee's work? (See also Ayush's recent update at
https://lore.kernel.org/git/CAE7as+ZpEwiNsDAozoZXqHRLOF3+hT++uo=mzZqEvTPovQN9uw@xxxxxxxxxxxxxx/)
It really depends on how unstable the base topic would be, but I
know Stolee is better than building his stuff on unusably unstable
crap, and that was the reason why I thought that updating this topic
on top of the same base would allow us to move forward faster, as it
would mean that everything would hopefully be ready _UNLESS_ the
change that needs to be made to the base topic is so extensive that
the topic on top would also need heavy updates _again_ once an
update to the base topic comes.
(Sorry, but sent before finishing).
Yes, it may be simpler to kick out a stalled topic and give it a
fresh restart when it becomes ready. If Derrick wants to go that
route, I am totally fine with that.
I'll see how things go this coming week as I page this series
back into my active work. If Ayush resubmits before I get to it,
then I won't be upset.
Thanks,
-Stolee
