Heya, Observe what happens if, on accident, rather than running a alias (amendall), the 'tab' didn't catch on: $ git am ^C $ # ok, now what do I do? $ git status # On branch checker-caching nothing to commit (working directory clean) $ # looks like everything is ok, great $ # ... some time later $ # same thing happens $ git am cat: /home/sverre/code/Melange/.git/rebase-apply/next: No such file or directory cat: /home/sverre/code/Melange/.git/rebase-apply/utf8: No such file or directory cat: /home/sverre/code/Melange/.git/rebase-apply/keep: No such file or directory cat: /home/sverre/code/Melange/.git/rebase-apply/threeway: No such file or directory cat: /home/sverre/code/Melange/.git/rebase-apply/apply-opt: No such file or directory cat: /home/sverre/code/Melange/.git/rebase-apply/sign: No such file or directory cat: /home/sverre/code/Melange/.git/rebase-apply/next: No such file or directory /usr/local/libexec/git-core//git-am: line 319: test: : integer expression expected /usr/local/libexec/git-core//git-am: line 326: test: : integer expression expected $ # whoops?! Wouldn't it be nice if "git am" without any arguments just prints a usage message? Either that, or provides you with a way to bail out? Or if it'd clean up after itself so that it doesn't crash? -- Cheers, Sverre Rabbelier -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
