forked from git/git
-
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
Carry non-locking status value in the environment. #1004
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Very good! Could you please sign off the patch and force-push an update? |
If the user has specified '--no-lock-index' when calling git-status, it only seems reasonable that the user intends that option to be carried through to any child forks/procs as well. Currently, the '--no-lock-status' call is lost when submodules are checked. This change places the desired option into the environment, which is in turn passed down to all subsequent children. With cmd_status checking for '--no-lock--status' first from args then from environment, we're able to keep the option set in all children. Signed-off-by: J Wyman <jeremy.wyman@microsoft.com>
dscho
added a commit
that referenced
this pull request
Dec 20, 2016
These two patches are really a fixup to PR #1004. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Thank you! |
dscho
added a commit
to git-for-windows/build-extra
that referenced
this pull request
Dec 23, 2016
The `--no-lock-index` option of `git status` [is now also respected also in submodules](git-for-windows/git#1004). Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
dscho
added a commit
that referenced
this pull request
Jan 11, 2017
These two patches are really a fixup to PR #1004. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
dscho
added a commit
that referenced
this pull request
Jan 11, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Jan 18, 2017
These two patches are really a fixup to PR #1004. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
dscho
added a commit
that referenced
this pull request
Jan 18, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Jan 18, 2017
These two patches are really a fixup to PR #1004. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
dscho
added a commit
that referenced
this pull request
Jan 18, 2017
Carry non-locking status value in the environment.
git-for-windows-ci
pushed a commit
that referenced
this pull request
Jan 18, 2017
These two patches are really a fixup to PR #1004. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
git-for-windows-ci
pushed a commit
that referenced
this pull request
Jan 18, 2017
Carry non-locking status value in the environment.
git-for-windows-ci
pushed a commit
that referenced
this pull request
Jan 18, 2017
These two patches are really a fixup to PR #1004. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
git-for-windows-ci
pushed a commit
that referenced
this pull request
Jan 18, 2017
Carry non-locking status value in the environment.
git-for-windows-ci
pushed a commit
that referenced
this pull request
Jan 18, 2017
These two patches are really a fixup to PR #1004. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
git-for-windows-ci
pushed a commit
that referenced
this pull request
Jan 18, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Jan 24, 2017
These two patches are really a fixup to PR #1004. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
dscho
added a commit
that referenced
this pull request
Jan 24, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Jan 24, 2017
These two patches are really a fixup to PR #1004. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
dscho
added a commit
that referenced
this pull request
Jan 24, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Jan 24, 2017
These two patches are really a fixup to PR #1004. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
dscho
added a commit
that referenced
this pull request
Jan 24, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Jan 25, 2017
These two patches are really a fixup to PR #1004. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
git-for-windows-ci
pushed a commit
that referenced
this pull request
Sep 11, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Sep 11, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Sep 12, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Sep 19, 2017
Carry non-locking status value in the environment.
git-for-windows-ci
pushed a commit
that referenced
this pull request
Sep 20, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Sep 20, 2017
Carry non-locking status value in the environment.
git-for-windows-ci
pushed a commit
that referenced
this pull request
Sep 21, 2017
Carry non-locking status value in the environment.
git-for-windows-ci
pushed a commit
that referenced
this pull request
Sep 21, 2017
Carry non-locking status value in the environment.
git-for-windows-ci
pushed a commit
that referenced
this pull request
Sep 26, 2017
Carry non-locking status value in the environment.
git-for-windows-ci
pushed a commit
that referenced
this pull request
Sep 26, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Sep 26, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Oct 17, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Oct 19, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Oct 19, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Oct 19, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Oct 19, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Oct 19, 2017
Carry non-locking status value in the environment.
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 20, 2017
Carry non-locking status value in the environment.
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 20, 2017
Carry non-locking status value in the environment.
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 20, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Oct 20, 2017
Carry non-locking status value in the environment.
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 21, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Oct 23, 2017
Carry non-locking status value in the environment.
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 24, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Oct 30, 2017
Carry non-locking status value in the environment.
dscho
added a commit
that referenced
this pull request
Nov 1, 2017
Carry non-locking status value in the environment.
This comment has been minimized.
This comment has been minimized.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the user has specified '--no-lock-index' when calling git-status, it only seems reasonable that the user intends that option to be carried through to any child forks/procs as well. Currently, the '--no-lock-status' call is lost when submodules are checked. This change places the desired option into the environment, which is in turn passed down to all subsequent children.
With cmd_status checking for '--no-lock--status' first from args then from environment, we're able to keep the option set in all children.