On Mon, Nov 21, 2016 at 12:48 PM, Junio C Hamano <gits...@pobox.com> wrote: > Stefan Beller <sbel...@google.com> writes: > >> The discussion of the submodule checkout series revealed to me >> that a command is needed to move the git directory from the >> submodules working tree to be embedded into the superprojects git >> directory. > > You used "move" here, and "migrate" in the function name in 3/3, > both of which make sense. > > But "intern" sounds funny. Who is confined as a prisoner here? > North American English uses that verb as "serve as an intern", but > that does not apply here. The verb also is used in Lisp-ish > languages to mean the act of turning a string into a symbol, but > that does not apply here, either.
I was inspired by the latter as we ask Git to make the submodule "properly embedded" into the superproject, which is what I imagined is similar to the lisp interning. So I guess my imagination went to far and we rather want to invoke it via "git submodule migrategitdirs" ? But there you would ask "where are we migrating the git dirs to?", so it would be reasonable to expect 2 parameters (just like the mv command). So maybe "git submodule embedgitdirs" ?
