Re: Silly "git gc" UI issue.

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 19, 2018, 01:55 UTC
Message-ID: <xmqqmuy0ez8b.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <xmqqr2ncezdc.fsf@gitster-ct.c.googlers.com>

Junio C Hamano <gitster@pobox.com> writes:

Show 13 quoted lines

> It turns out that prune silently goes away given a bad expiry
>
>     $ git prune --expire=nyah ; echo $?
>     129
>
> Regardless of your originai "git gc" issue, we should make "prune"
> say something on this error.  And when we do so, I would think that
> error message will come before the final "error: failed to run
> prune".
>
> Or perhaps we do so and then squelch "error: failed to run prune",
> trusting that a corrected "git prune" will always say something when
> it fails.

It turns out that

    $ git worktree prune --expire=nyah

shares the same issue.  I'll take a look at OPT_EXPIRY_DATE() thing.