diff options
author | Jeff King <peff@peff.net> | 2016-02-29 06:01:56 -0500 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2016-02-29 09:24:47 -0800 |
commit | fc7d47f0dd4f041af2ed2004700f18b635f3b204 (patch) | |
tree | d41e5fcb4f10c3e12497dea3940ac33234abcd23 /t/t3210-pack-refs.sh | |
parent | t1515: add tests for rev-parse out-of-repo helpers (diff) | |
download | tgif-fc7d47f0dd4f041af2ed2004700f18b635f3b204.tar.xz |
rev-parse: let some options run outside repository
Once upon a time, you could use "--local-env-vars" and
"--resolve-git-dir" outside of any git repository, but they
had to come first on the command line. Commit 68889b4
(rev-parse: remove restrictions on some options, 2013-07-21)
put them into the normal option-parsing loop, fixing the
latter. But it inadvertently broke the former, as we call
setup_git_directory() before starting that loop.
We can note that those options don't care even conditionally
about whether we are in a git repo. So it's fine if we
simply wait to setup the repo until we see an option that
needs it.
However, there is one special exception we should make:
historically, rev-parse will set up the repository and read
config even if there are _no_ options. Some of the
tests in t1300 rely on this to check "git -c $config"
parsing. That's not mirroring real-world use, and we could
tweak the test. But t0002 uses a bare "git rev-parse" to
check "are we in a git repository?". It's plausible that
real-world scripts are relying on this.
So let's cover this case specially, and treat an option-less
"rev-parse" as "see if we're in a repo".
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t3210-pack-refs.sh')
0 files changed, 0 insertions, 0 deletions