On Friday, February 27, 2015 at 9:00:50 PM UTC+1, saurabh arora wrote: > > Release notes for 1.9.2 has a comment for the fixes made from ver 1.9.1 “git > mv" that moves a submodule forgot to adjust the array that uses to keep > track of which submodules were to be moved to update its configuration.” > > Want to know what the actual issue was? >
According to one of the maintainer "What's cooking" mails [1]: * jk/mv-submodules-fix (2014-03-17) 2 commits > (merged to 'next' on 2014-03-17 at 7cae3b1) > + mv: prevent mismatched data when ignoring errors. > + builtin/mv: fix out of bounds write > "git mv" that moves a submodule forgot to adjust the array that > uses to keep track of which submodules were to be moved to update > its configuration. If you want more information, try searching the archives [2] for the above commit messages. You'll find plenty of discussion there. [1] http://article.gmane.org/gmane.comp.version-control.git/243907/match=what's+cooking+git+mar+2014+06+tue+25 [2] http://dir.gmane.org/gmane.comp.version-control.git -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
