Etienne Samson ef7d7defd6 worktree: unlock should return 1 when the worktree isn't locked ...

The documentation states that git_worktree_unlock returns 0 on success,
and 1 on success if the worktree wasn't locked. Turns out we were
returning 0 in any of those cases.

(cherry picked from commit 59c2e70eee)

2018-10-26 14:58:51 +02:00

..

config.c

config: open configuration in commondir

2017-02-13 10:28:15 +01:00

merge.c

repository: rename path_repository and path_gitlink

2017-02-13 11:07:52 +01:00

open.c

worktree: implement git_worktree_open_from_repository

2017-03-17 09:26:13 +01:00

reflog.c

worktree: Read worktree specific reflog for HEAD

2018-05-30 08:12:54 +02:00

refs.c

worktree: switch over worktree pruning to an opts structure

2017-05-05 15:39:25 +02:00

repository.c

tests: ensure worktrees' head have owners too

2018-05-30 08:12:53 +02:00

submodule.c

worktree: introduce git_worktree_add options

2017-05-02 12:39:29 +02:00

worktree_helpers.c

tests: implement worktree helpers

2017-02-13 10:13:02 +01:00

worktree_helpers.h

tests: implement worktree helpers

2017-02-13 10:13:02 +01:00

worktree.c

worktree: unlock should return 1 when the worktree isn't locked

2018-10-26 14:58:51 +02:00