Tim Schumacher writes:
> it is located at the top of the while() loop. Giving an example is nice, but
> wouldn't
> it be better to say something like the following?
>
> /*
>* Check if av[0] is a command before seeing if it is an
>* alias to avoid taking over existing
On 17.09.18 17:37, Junio C Hamano wrote:
Tim Schumacher writes:
On 08.09.18 15:28, Duy Nguyen wrote:
On Sat, Sep 8, 2018 at 12:44 AM Tim Schumacher wrote:
+ /*
+* It could be an alias -- this works around the insanity
* of overriding "git
Tim Schumacher writes:
> On 08.09.18 15:28, Duy Nguyen wrote:
>> On Sat, Sep 8, 2018 at 12:44 AM Tim Schumacher wrote:
>>> + /*
>>> +* It could be an alias -- this works around the insanity
>>> * of overriding "git log" with "git show" by having
On 08.09.18 15:28, Duy Nguyen wrote:
On Sat, Sep 8, 2018 at 12:44 AM Tim Schumacher wrote:
+ /*
+* It could be an alias -- this works around the insanity
* of overriding "git log" with "git show" by having
* alias.log = show
On Sat, Sep 8, 2018 at 12:44 AM Tim Schumacher wrote:
> + /*
> +* It could be an alias -- this works around the insanity
> * of overriding "git log" with "git show" by having
> * alias.log = show
> */
I think this
Aliases can only contain non-alias git commands and their
arguments, not other user-defined aliases. Resolving further
(nested) aliases is prevented by breaking the loop after the
first alias was processed. Git then fails with a command-not-found
error.
Allow resolving nested aliases by not
6 matches
Mail list logo