I'm struggling with a bug that I found introduced in git v2.13.2. The bug was not reproducible in v2.13.1. The issue is that using arguments like "@{-1}" to aliases causes those curly braces to be removed, so once the command is executed after alias processing the argument looks like "@-1". This breaks any aliases you have that wrap `git log` and such. I originally opened the bug on the Git for Windows project (since I use Git mostly on Windows): https://github.com/git-for-windows/git/issues/1220 After digging into the code of run-command.c some more, I have a change that fixes the issue but it doesn't feel like the right solution. Furthermore, the function I'm modifying doesn't seem to have been changed in the diff between v2.13.1 and v2.13.2. I'll provide my diff at the bottom of this email for those curious as to what I've modified. I was not able to reproduce this bug on Linux. However, the way aliases get expanded seems extremely wasteful. Essentially if an alias already has $@ in it, Git shouldn't try to insert another one. This results in the alias being repeated multiple times. I'll give you an example (Note there's a ton of detail in the github post linked earlier, and most of this is already there). Here is the alias being used for a test: [alias] lgtest = !git log --oneline \"$@\" And here is the command I invoke for the test: $ git lgtest @{-1} I should get logs for the previously-checked-out branch. When `prepare_shell_cmd()` is called in run-command.c, it gets expanded like so: + [0] "sh" const char * + [1] "-c" const char * + [2] "git log --oneline \"$@\" \"$@\"" const char * + [3] "git log --oneline \"$@\"" const char * + [4] "@{-1}" const char * With my modifications (again, patch inline below) I get this: + [0] "sh" const char * + [1] "-c" const char * + [2] "git log --oneline \"$@\"" const char * + [3] "@{-1}" const char * The second version looks much better. I think the constant nesting of commands inside each other that the first version does is somehow causing curly braces to be removed. I don't understand enough about shell processing to know why it would do this. Essentially I don't feel like I'm addressing the root cause here. I hope that someone has the time to take a peek and point me in the right direction. If I can make sense of this maybe I can make a proper fix somewhere. Here is the patch: diff --git a/run-command.c b/run-command.c index 31fc5ea86e..39bab7f5b2 100644 --- a/run-command.c +++ b/run-command.c @@ -261,10 +261,10 @@ static const char **prepare_shell_cmd(struct argv_array *out, const char **argv) if (!argv[1]) argv_array_push(out, argv[0]); else - argv_array_pushf(out, "%s \"$@\"", argv[0]); + argv_array_pushf(out, "%s", argv[0]); } - argv_array_pushv(out, argv); + argv_array_pushv(out, argv+1); return out->argv; }