Etienne Samson 59c2e70eee 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.

2018-08-17 00:51:51 +02:00

..

bare.c

tests: worktree/bare: test some paths

2018-06-29 14:39:14 +02:00

config.c

treewide: remove use of C++ style comments

2018-07-13 08:25:12 +02:00

merge.c

Convert usage of git_buf_free to new git_buf_dispose

2018-06-10 19:34:37 +02:00

open.c

tests: add a helper to build sandbox subpaths quickly

2018-06-29 14:39:13 +02:00

reflog.c

worktree: Read worktree specific reflog for HEAD

2018-03-27 19:04:05 +02:00

refs.c

Convert usage of git_buf_free to new git_buf_dispose

2018-06-10 19:34:37 +02:00

repository.c

tests: ensure worktrees' head have owners too

2018-04-10 23:50:19 +02:00

submodule.c

Convert usage of git_buf_free to new git_buf_dispose

2018-06-10 19:34:37 +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-08-17 00:51:51 +02:00