Richard Hansen wrote: > On 2013-11-11 18:50, Felipe Contreras wrote: > > On Mon, Nov 11, 2013 at 5:25 PM, Junio C Hamano <gits...@pobox.com> wrote: > >> Felipe Contreras <felipe.contre...@gmail.com> writes: > >> > >>> So that we can convert the exported ref names. > >>> > >>> Signed-off-by: Felipe Contreras <felipe.contre...@gmail.com> > >>> --- > >> > >> I thought that the discussion agreed this option should not be > >> called --refspec but something like --refmap? > > > > I don't know what you agreed to, > > http://article.gmane.org/gmane.comp.version-control.git/237473 > > > but I didn't agree to anything. > > Based on your silence I too thought that you had agreed.
Given that my opinion is regarded as inferior by those in the discussion, I don't see why I should share it, specially since when I do, it's considered toxic if I disagree. > > What you pass to this option is a refspec, so it makes sense to name > > the option --refspec. > > As discussed in that thread, it's not really the same thing as a refspec > used in push or fetch. In those commands, the refspec specifies two > separable things: what to transfer, and how to translate refs names > between the remote and local repositories. IIUC, the fast-export > --refspec argument only specifies how to translate ref names, not what > gets transferred. Does it? % git config remote.origin.fetch '+refs/heads/*:refs/remotes-test/origin/*' % git fetch origin master From /home/felipec/dev/git * branch master -> FETCH_HEAD * [new branch] master -> refs/remotes-test/origin/master In this case remote.origin.fetch is determining how to translate ref names, not what gets transferred, *exactly* the same as we are doing with --refspec. And as far as I know, remote.origin.fetch is a refspec. -- Felipe Contreras -- 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 http://vger.kernel.org/majordomo-info.html
