-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New experimental stash builtin fails with changes in submodule [recipe included] #1820
Comments
Can you also report this, with MVCE, on the git developers list [email protected] The [email protected] list only accepts plain text - any HTML part is deemed as indicating spam! The list is open and will cc all contributors The list archive is at "https://public-inbox.org/git/?q= " with a recent report here |
@PhilipOakley Sure. Will do. I'm following the git ML as well. |
@t-b as that thread ended up reverting something that was not even related to the built-in stash, I am now puzzled whether this issue still persists for you? |
(In particular since your reproducer fails to reproduce the issue with v2.19.0...) If it is fixed, please close the ticket. |
Okay, I'll go ahead and assume that the issue was fixed by that partial revert. |
@dscho Nope, I can still reproduce it with 2.19.1.windows.1. |
sigh I could have done something about that in the past day, before v2.19.1 was released. |
Whoops, forgot to re-open. |
I think I found the culprit: dscho/git@git-for-windows:master...fix-built-in-rebase-autostash. As stated in the commit message, this lacks a regression test. @t-b how about it? Could you turn your MCVE into a test case, say, for |
It has been reported that dirty submodules cause problems with the built-in rebase when it is asked to autostash. The symptom is: fatal: Unexpected stash response: '' This patch adds a regression test that demonstrates that bug. Original report: git-for-windows#1820 Signed-off-by: Johannes Schindelin <[email protected]>
Since we cannot stash dirty submodules, there is no use in requiring them to be clean (or stash them when they are not). This brings the built-in rebase in line with the previous, scripted version, which also did not care about dirty submodules (but it was admittedly not very easy to figure that out). This fixes git-for-windows#1820 Signed-off-by: Johannes Schindelin <[email protected]>
For lurkers: the patch series was contributed to the Git mailing list. |
It has been reported that dirty submodules cause problems with the built-in rebase when it is asked to autostash. The symptom is: fatal: Unexpected stash response: '' This patch adds a regression test that demonstrates that bug. Original report: git-for-windows#1820 Signed-off-by: Johannes Schindelin <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
It has been reported that dirty submodules cause problems with the built-in rebase when it is asked to autostash. The symptom is: fatal: Unexpected stash response: '' This patch adds a regression test that demonstrates that bug. Original report: git-for-windows#1820 Signed-off-by: Johannes Schindelin <[email protected]> Signed-off-by: Junio C Hamano <[email protected]> Signed-off-by: Johannes Schindelin <[email protected]>
Since we cannot stash dirty submodules, there is no use in requiring them to be clean (or stash them when they are not). This brings the built-in rebase in line with the previous, scripted version, which also did not care about dirty submodules (but it was admittedly not very easy to figure that out). This fixes git-for-windows#1820 Signed-off-by: Johannes Schindelin <[email protected]> Signed-off-by: Junio C Hamano <[email protected]> Signed-off-by: Johannes Schindelin <[email protected]>
It has been reported that dirty submodules cause problems with the built-in rebase when it is asked to autostash. The symptom is: fatal: Unexpected stash response: '' This patch adds a regression test that demonstrates that bug. Original report: git-for-windows#1820 Signed-off-by: Johannes Schindelin <[email protected]> Signed-off-by: Junio C Hamano <[email protected]> Signed-off-by: Johannes Schindelin <[email protected]>
Since we cannot stash dirty submodules, there is no use in requiring them to be clean (or stash them when they are not). This brings the built-in rebase in line with the previous, scripted version, which also did not care about dirty submodules (but it was admittedly not very easy to figure that out). This fixes git-for-windows#1820 Signed-off-by: Johannes Schindelin <[email protected]> Signed-off-by: Junio C Hamano <[email protected]> Signed-off-by: Johannes Schindelin <[email protected]>
It has been reported that dirty submodules cause problems with the built-in rebase when it is asked to autostash. The symptom is: fatal: Unexpected stash response: '' This patch adds a regression test that demonstrates that bug. Original report: #1820 Signed-off-by: Johannes Schindelin <[email protected]> Signed-off-by: Junio C Hamano <[email protected]> Signed-off-by: Johannes Schindelin <[email protected]>
Since we cannot stash dirty submodules, there is no use in requiring them to be clean (or stash them when they are not). This brings the built-in rebase in line with the previous, scripted version, which also did not care about dirty submodules (but it was admittedly not very easy to figure that out). This fixes #1820 Signed-off-by: Johannes Schindelin <[email protected]> Signed-off-by: Junio C Hamano <[email protected]> Signed-off-by: Johannes Schindelin <[email protected]>
Setup
defaults?
to the issue you're seeing?
Nope
Details
Bash
Minimal, Complete, and Verifiable example
this will help us understand the issue.
That it works.
The text was updated successfully, but these errors were encountered: