Re: [PATCH v3] stash: honor --no-overwrite-ignore with --all
- From
Pushkar Singh <pushkarkumarsingh1970@gmail.com>
- Date
- Feb 3, 2026, 20:07 UTC
- Message-ID
- <CALE2CrSwN7AB05Qd7G7LOGjSNu3=BbLLVBfoNf5a95SMRBm5WQ@mail.gmail.com>
- In-Reply-To
- <CABPp-BG6wM4p0wAizEppT7QdtY710xBJ8NwgfzrDpP3Oyg=a0w@mail.gmail.com>
Hi Elijah,
Thank you for taking the time to explain this so clearly.
You are absolutely right. I misunderstood what you meant by “basis” and also approached this patch from the implementation side instead of starting from a concrete user problem.
I also realize now that I incorrectly stacked this on top of my local changes instead of rebasing and editing the previous version, which made the patch impossible to apply upstream. Sorry about that.
Given your feedback, I agree that I need to step back and rethink this from a user perspective (what real workflow is broken today, how -a should behave, and whether any new flags even make sense here), rather than trying to force consistency at a low level.
I will drop this series for now, spend time understanding stash behavior and the broader context you pointed out, and only resend if I can clearly articulate a user-driven problem with a clean patch based directly on upstream.
Thanks again for your patience and guidance.
Pushkar