diff options
author | Eric Sunshine <sunshine@sunshineco.com> | 2020-08-09 18:53:16 -0400 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2020-08-10 09:24:11 -0700 |
commit | ccf236a23adb5cfb4e5285daad083149458d7828 (patch) | |
tree | e0da2fb8404edc10ad50379f85d928038911e1fd /builtin/mailsplit.c | |
parent | Git 2.28 (diff) | |
download | tgif-ccf236a23adb5cfb4e5285daad083149458d7828.tar.xz |
init: disallow --separate-git-dir with bare repository
The purpose of "git init --separate-git-dir" is to separate the
repository from the worktree. This is true even when --separate-git-dir
is used on an existing worktree, in which case, it moves the .git/
subdirectory to a new location outside the worktree.
However, an outright bare repository (such as one created by "git init
--bare"), has no worktree, so using --separate-git-dir to separate it
from its non-existent worktree is nonsensical. Therefore, make it an
error to use --separate-git-dir on a bare repository.
Implementation note: "git init" considers a repository bare if told so
explicitly via --bare or if it guesses it to be so based upon
heuristics. In the explicit --bare case, a conflict with
--separate-git-dir is easy to detect early. In the guessed case,
however, the conflict can only be detected once "bareness" is guessed,
which happens after "git init" has begun creating the repository.
Technically, we can get by with a single late check which would cover
both cases, however, erroring out early, when possible, without leaving
detritus provides a better user experience.
Signed-off-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin/mailsplit.c')
0 files changed, 0 insertions, 0 deletions