From: Anthony Baire Date: Wed, 27 Nov 2013 20:30:51 GMT Subject: Re: [PATCH] subtree: fix argument validation in add/pull/push Message-ID: <5296567B.5080704@irisa.fr> In-Reply-To: <87siuhfy9q.fsf@thomasrast.ch> On 27/11/2013 20:19, Thomas Rast wrote: > Anthony Baire writes: > >> When working with a remote repository add/pull/push do not accept a >> as parameter but just a . They should accept any >> well-formatted ref name. > [...] >> - update the doc to use instead of > [...] >> OPTS_SPEC="\ >> git subtree add --prefix= >> -git subtree add --prefix= >> +git subtree add --prefix= >> git subtree merge --prefix= >> -git subtree pull --prefix= >> -git subtree push --prefix= >> +git subtree pull --prefix= >> +git subtree push --prefix= >> git subtree split --prefix= > [...] >> @@ -68,7 +68,7 @@ COMMANDS >> -------- >> add:: >> Create the subtree by importing its contents >> - from the given or and remote . >> + from the given or and remote . > AFAICS you are changing refspec->commit in the manpage, but commit->ref > in the usage message for 'subtree add'? How does this line up? > 'git subtree add' accepts a commit when working with the local repository and a ref when working with a remote repository: git subtree add --prefix= git subtree add --prefix= but the manpage was no in sync with the code. I fixed it for the local case too. Anthony