submodule --update insufficiently verbose
When a "git submodule --update" fails, e.g., due to a dirty working directory in one of the submodules, nothing is printed out indicating the submodule or directory in which the failure occurred. This seems like a usability bug to me.
Thanks,
Signature · 3 lines
Dave Abrahams BoostPro Computing http://www.boostpro.com
Quoted 4 lines · Dave Abrahams
When a "git submodule --update" fails, e.g., due to a dirty working directory in one of the submodules, nothing is printed out indicating the submodule or directory in which the failure occurred. This seems like a usability bug to me.
I assume you mean 'git submodule update'. What git version is this, and how do you reproduce? I get a message like
error: Your local changes to the following files would be overwritten by checkout:
foo
Please, commit your changes or stash them before you can switch branches. Aborting
Unable to checkout '1fac3675a8c65b14e0a98e0136b5c43db97706fe' in submodule path 'sub'
in a simple test. I am using a development version, but a brief glance at the history seems to indictate that the 'Unable to ... in submodule ...' has always been there.
Signature · 2 lines
Thomas Rast
trast@{inf,student}.ethz.ch