[PATCH] branch: change the error messages to be more meaningful

2017-07-30 Thread Kaartic Sivaraam
The error messages shown when the branch command is misused by supplying it wrong number of parameters wasn't meaningful. That's because it used the the phrase "too many branches" assuming all parameters to be "valid" branch names. It's not always the case as exemplified below, $ git branc

[PATCH] branch: change the error messages to be more meaningful

2017-07-30 Thread Kaartic Sivaraam
The error messages shown when the branch command is misused by supplying it wrong number of parameters wasn't meaningful. That's because it used the the phrase "too many branches" assuming all parameters to be "valid" branch names. It's not always the case as exemplified below, $ git branc

Re: [PATCH] branch: change the error messages to be more meaningful

2017-07-25 Thread Kaartic Sivaraam
The second patch differs from the first one only in the commit message. -- Kaartic

[PATCH] branch: change the error messages to be more meaningful

2017-07-25 Thread Kaartic Sivaraam
The error messages shown when the branch command is misused by supplying it wrong number of parameters wasn't meaningful. That's because it used the the phrase "too many branches" assuming all parameters to be "valid" branch names. It's not always the case as exemplified below, $ git branc

[PATCH] branch: change the error messages to be more meaningful

2017-07-25 Thread Kaartic Sivaraam
The error messages shown when the branch command is misused by supplying it wrong number of parameters wasn't meaningful as it used the the phrase, "too many branches" which is not meaningful in the following case, $ git branch foo * master $ git branch -m foo fo