Re: [PATCH v3 1/2] am: handle stray $dotest directory

2013-06-18 Thread Ramkumar Ramachandra
Junio C Hamano wrote: Will replace what has been queued on 'pu'. ... after fixing an indentation error, that is. Where did the error occur? I thought I taught my Emacs to always indent properly. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to

Re: [PATCH v3 1/2] am: handle stray $dotest directory

2013-06-18 Thread Junio C Hamano
Ramkumar Ramachandra artag...@gmail.com writes: Junio C Hamano wrote: Will replace what has been queued on 'pu'. ... after fixing an indentation error, that is. Where did the error occur? I think you can compare what is in 'pu' and what you sent out without asking. -- To unsubscribe from

Re: [PATCH v3 1/2] am: handle stray $dotest directory

2013-06-18 Thread Ramkumar Ramachandra
Junio C Hamano wrote: Where did the error occur? I think you can compare what is in 'pu' and what you sent out without asking. Ah, I sent out the series before I taught Emacs to indent properly. Thanks. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message

Re: [PATCH v3 1/2] am: handle stray $dotest directory

2013-06-17 Thread Junio C Hamano
Junio C Hamano gits...@pobox.com writes: Will replace what has been queued on 'pu'. ... after fixing an indentation error, that is. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at

Re: [PATCH v3 1/2] am: handle stray $dotest directory

2013-06-16 Thread Junio C Hamano
Ramkumar Ramachandra artag...@gmail.com writes: else + # Possible stray $dotest directory in the independent-run + # case; in the --rebasing case, it is upto the caller + # (git-rebase--am) to take care of stray directories. + if test -d $dotest test -z $rebasing The

[PATCH v3 1/2] am: handle stray $dotest directory

2013-06-15 Thread Ramkumar Ramachandra
The following bug has been observed: $ git am # no input file ^C $ git am --abort Resolve operation not in progress, we are not resuming. This happens because the following test fails: test -d $dotest test -f $dotest/last test -f $dotest/next and the codepath for an am in-progress