Skip to content

refdb: catch additional per-worktree refs#4124

Merged
pks-t merged 1 commit intolibgit2:masterfrom
pks-t:pks/worktree-refs
Feb 17, 2017
Merged

refdb: catch additional per-worktree refs#4124
pks-t merged 1 commit intolibgit2:masterfrom
pks-t:pks/worktree-refs

Conversation

@pks-t
Copy link
Copy Markdown
Member

@pks-t pks-t commented Feb 14, 2017

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/

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 pks-t force-pushed the pks/worktree-refs branch from 3b4ea31 to 6da6b42 Compare February 15, 2017 08:07
@pks-t pks-t merged commit 021f494 into libgit2:master Feb 17, 2017
@pks-t pks-t deleted the pks/worktree-refs branch February 21, 2017 10:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant