Repository navigation
refdb: catch additional per-worktree refs - #4124
Merged
pks-t merged 1 commit intoFeb 17, 2017
Merged
pks-t merged 1 commit into
pks-t merged 1 commit into
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
The upstream git.git project currently identifies all references inside of `refs/bisect/` as well as `HEAD` as per-worktree references. This is already incorrect and is currently being fixed by an in-flight topic [1]. The new behavior will be to match all pseudo-references outside of the `refs/` hierarchy as well as `refs/bisect/`. Our current behavior is to mark a selection of pseudo-references as per-worktree, only. This matches more pseudo-references than current git, but forgets about `refs/bisect/`. Adjust behavior to match the in-flight topic, that is classify the following references as per-worktree: - everything outside of `refs/` - everything inside of `refs/bisect/` [1]: <20170213152011.12050-1-pclouds@gmail.com>
pks-t
force-pushed
the
pks/worktree-refs
branch
from
3b4ea31 to
6da6b42
Compare
February 15, 2017 08:07
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The upstream git.git project currently identifies all references inside
of refs/bisect/ as well as HEAD as per-worktree references. This is
already incorrect and is currently being fixed by an in-flight topic
1. The new behavior will be to match all pseudo-references outside of
the refs/ hierarchy as well as refs/bisect/.
Our current behavior is to mark a selection of pseudo-references as
per-worktree, only. This matches more pseudo-references than current
git, but forgets about refs/bisect/. Adjust behavior to match the
in-flight topic, that is classify the following references as
per-worktree: