Re: [PATCH 3/3] check-ref-format doc: --branch validates and expands

2017-10-17 Thread Jeff King
On Wed, Oct 18, 2017 at 05:55:18AM +0900, Junio C Hamano wrote: > I'll take these three to replace what I tentatively queued, not > necessarily because I like the change in 1/3 better, but because > these are explained much better; besides I prefer a version that at > least two people deeply looke

Re: [PATCH 3/3] check-ref-format doc: --branch validates and expands

2017-10-17 Thread Jonathan Nieder
Junio C Hamano wrote: > Jonathan Nieder writes: >> From: Junio C Hamano >> >> "git check-ref-format --branch $name" feature was originally >> introduced (and was advertised) as a way for scripts to take any >> end-user supplied string (like "master", "@{-1}" etc.) and see if it >> is usable when

Re: [PATCH 3/3] check-ref-format doc: --branch validates and expands

2017-10-17 Thread Junio C Hamano
Jonathan Nieder writes: > From: Junio C Hamano > > "git check-ref-format --branch $name" feature was originally > introduced (and was advertised) as a way for scripts to take any > end-user supplied string (like "master", "@{-1}" etc.) and see if it > is usable when Git expects to see a branch n

[PATCH 3/3] check-ref-format doc: --branch validates and expands

2017-10-17 Thread Jonathan Nieder
From: Junio C Hamano "git check-ref-format --branch $name" feature was originally introduced (and was advertised) as a way for scripts to take any end-user supplied string (like "master", "@{-1}" etc.) and see if it is usable when Git expects to see a branch name, and also obtain the concrete bra