Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Git Bash does not start at drive root #204

Closed
linquize opened this issue Jun 17, 2015 · 2 comments
Closed

Git Bash does not start at drive root #204

linquize opened this issue Jun 17, 2015 · 2 comments

Comments

@linquize
Copy link

I start Git Bash via Shell Context Menu (Git Bash Here).
If it is a drive root, such as C:\ or D:,
Git Bash does not show up.

git 2.4.0.windows.1 64-bit
@dscho
Copy link
Member

dscho commented Jun 17, 2015

git 2.4.0.windows.1 64-bit

This is not the latest release.

I start Git Bash via Shell Context Menu (Git Bash Here).
If it is a drive root, such as C:\ or D:,
Git Bash does not show up.

Is this different from #176?

@linquize
Copy link
Author

oops, duplicate issue

jeffhostetler pushed a commit to jeffhostetler/git that referenced this issue Oct 25, 2019
@derrickstolee
Merge pull request git-for-windows#204: sparse-checkout: don't update…
afc37de 
… sparse-checkout file on error

If the index has an unstaged change in a file that will be dropped
by a change to the sparse-checkout file, then the index update
will fail. If this happens during 'git sparse-checkout set', then
the entire command will fail. However, the sparse-checkout file is
still updated, so the working directory is in a half-finished state.

Update the sparse-checkout builtin to run `unpack_trees()`
directly instead of through an external `git read-tree` process.
While doing so, allow passing a set of patterns, so we can
validate the patterns before trying to write to the sparse-checkout
file.

Also, write sparse-checkout under a .lock and take the
sparse-checkout lock around the unpack_trees() check.

Resolves git-for-windows#198.

Merging with admin privileges because mac builds are broken
due to external dependencies.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dscho @linquize