Re: git checkout error

2012-10-10 Thread Angelo Borsotti
Hi Junio > It is not difficult. The discussion on this list is usually done > via patches, and without one, constant talking is buried in other > noise and often go unnoticed. Could you accept for very small changes also the simple indication of the change itself instead of a patch? > > There i

Re: git checkout error

2012-10-10 Thread Junio C Hamano
Angelo Borsotti writes: > Why it is so difficult to convince people to make documentation better? It is not difficult. The discussion on this list is usually done via patches, and without one, constant talking is buried in other noise and often go unnoticed. There is however an issue about doc

Re: git checkout error

2012-10-10 Thread Angelo Borsotti
Junio, giving the user a better error message is certainly an improvement. But would not be another improvement to describe better the command syntax so as to help the user write the command right in the first place? After all, what is the syntax section in commands for? If I had seen in the synta

Re: git checkout error

2012-10-09 Thread Junio C Hamano
Angelo Borsotti writes: > The man page describes --track and --no-track as "options". But the problem you observed is *not* about --track or --no-track. It is about the "-b " option. You used the -b option that requires an argument, and as that argument, you gave a string "--no-track", as if y

Re: git checkout error

2012-10-09 Thread Angelo Borsotti
Hi Andreas, > > -b requires an argument , which you specify as --no-track > here. is topic, and the rest is interpreted as . > The man page describes --track and --no-track as "options". This is why a reader thinks that they can be specified in any order. It is also very counter-intuitive to thi

Re: git checkout error

2012-10-09 Thread Junio C Hamano
Andreas Schwab writes: > Angelo Borsotti writes: > >> If they are specified after -b, the command seems to behave as if -b >> was not specified, e.g.: >> >> $ git checkout -b --no-track topic remotes/origin/master > > -b requires an argument , which you specify as --no-track > here. is topic,

Re: git checkout error

2012-10-09 Thread Andreas Schwab
Angelo Borsotti writes: > If they are specified after -b, the command seems to behave as if -b > was not specified, e.g.: > > $ git checkout -b --no-track topic remotes/origin/master -b requires an argument , which you specify as --no-track here. is topic, and the rest is interpreted as . > f