> Hm, can you say more about the context? From a certain point of view,
> it might make sense for that command to succeed instead: if the repo
> is already unshallow, then why should't "fetch --unshallow" complain
> instead of declaring victory?
A fellow in #git on Freenode was writing a script f
Jonathan Nieder writes:
>> test_expect_success 'showing the superproject correctly' '
>
> With the two tweaks mentioned above,
> Reviewed-by: Jonathan Nieder
I agree with the fixes to the test titles suggested, so I'll queue
the patch with the fixes squashed in. Hearing "yeah, the titles
were
Hi,
Øystein Walle wrote:
> Running `git fetch --unshallow` on a repo that is not in fact shallow
> produces a fatal error message.
Hm, can you say more about the context? From a certain point of view,
it might make sense for that command to succeed instead: if the repo
is already unshallow, the
Running `git fetch --unshallow` on a repo that is not in fact shallow
produces a fatal error message. Add a helper to rev-parse that scripters
can use to determine whether a repo is shallow or not.
Signed-off-by: Øystein Walle
---
Documentation/git-rev-parse.txt | 3 +++
builtin/rev-parse.c
4 matches
Mail list logo