On Mon, Oct 29, 2012 at 06:45:44AM -0400, W. Trevor King wrote: > > > Ah, good, then we *are* all using the option for the same thing. > > > > That makes me more comfortable. Your patch adds support for setting the > > variable initially. Does it need any special magic for maintenance, or > > is it something that would always be updated by hand? > > Everyone we've heard from so far interprets the setting as “pull from > $branch in the remote repository $url to update the submodule”. With > Phil's export, that would become > > $ git submodule foreach 'git checkout "$submodule_branch" && git pull' > $ git commit -a -m "Updated submodules" > $ git push > > As Nahor mentioned on the 23rd, there are a number of ways that the > upstream branch could disappear, but Git has no way to know what the > new branch setting should be. This means that even if we make “pull > from $branch” interpretation official, we still couldn't do anything > slick about updating it. So, yes, it will be updated by hand.
OK. Can you send an updated version of the patch that summarizes the situation in the commit message? I also think it is probably worth saying something in the documentation for the feature like "Note that this value is not actually used by git; however, some external tools and workflows may make use of it." -Peff -- 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
