-
-
Notifications
You must be signed in to change notification settings - Fork 402
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
Git status shows all files as untracked #598
Labels
Comments
I stumbled upon this, too. I'm using python 2.7.6 and the latest dulwich from git on Ubun tu 16.04. This is the test code I wrote:
This is the output:
|
Glad to hear at least it's not just me - I've not looked at anything today, but I might clone this repo and have a poke around the existing tests tomorrow |
alistair-broomhead
added a commit
to alistair-broomhead/dulwich
that referenced
this issue
Jan 6, 2018
Looking at the code in porcelain.path_to_tree_path, this looks like there was an attempt at this in 85b5383, however relpath is non-destructive, and has no effect unless the result is assigned to something. If this were assigned when path is relative, then relpath would assume path was at root, and so we must check that the path is absolute before calling relpath. Fixes jelmer#598
alistair-broomhead
added a commit
to alistair-broomhead/dulwich
that referenced
this issue
Jan 13, 2018
Looking at the code in porcelain.path_to_tree_path, this looks like there was an attempt at this in 85b5383, however relpath is non-destructive, and has no effect unless the result is assigned to something. If this were assigned when path is relative, then relpath would assume path was at root, and so we must check that the path is absolute before calling relpath. Fixes jelmer#598
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is observed using a fresh pipenv with only dulwich==0.18.6 installed using python3.6 from pyenv on OSX
This is obviously not consistent with the way that git itself describes the repository state. Is this by design or a known issue? Are there any known work-arounds? If not I'm happy to give any spare cycles to have a dig into improving things, even if that's just by contributing docs.
The text was updated successfully, but these errors were encountered: