From: Duy Nguyen <pclouds@gmail.com>
Date: Sat, 08 Sep 2018 13:34:34 GMT
Subject: Re: [RFC PATCH v4 2/3] Show the call history when an alias is looping
Message-ID: <CACsJy8C+VPGyu1D6yeFU3eqzwusv_Q=tobZgvXOtZ=5gYak5dg@mail.gmail.com>
In-Reply-To: <20180907224430.23859-2-timschumi@gmx.de>

On Sat, Sep 8, 2018 at 12:44 AM Tim Schumacher <timschumi@gmx.de> wrote:
>
> Just printing the command that the user entered is not particularly
> helpful when trying to find the alias that causes the loop.
>
> Print the history of substituted commands to help the user find the
> offending alias. Mark the entrypoint of the loop with "<==" and the
> last command (which looped back to the entrypoint) with "==>".

An even simpler way to give this information is simply suggest the
user tries again with GIT_TRACE=1. All alias expansion is shown there
and we teach the user about GIT_TRACE. But your approach is probably
more user friendly.
-- 
Duy