{"thread":{"id":"29314","subject":"[bug] submodule --update insufficiently verbose","startedAt":"2012-01-08T02:33:00Z","lastAt":"2012-01-10T10:43:24Z","messageCount":2,"participants":["Dave Abrahams","Thomas Rast"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"182081","messageId":"m239bqnctf.fsf@pluto.luannocracy.com","threadId":"29314","inReplyTo":null,"subject":"[bug] submodule --update insufficiently verbose","fromName":"Dave Abrahams","fromEmail":"dave@boostpro.com","sentAt":"2012-01-08T02:33:00Z","receivedAt":"2012-01-08T02:33:00Z","isPatch":false,"sender":{"key":"dave@boostpro.com","avatar":"https://gravatar.com/avatar/df0921f05114687777894565de21c052fb137ba7c303a399528b43d08833f065?d=mp&s=160"},"body":"\nWhen a \"git submodule --update\" fails, e.g., due to a dirty working\ndirectory in one of the submodules, nothing is printed out indicating\nthe submodule or directory in which the failure occurred.  This seems\nlike a usability bug to me.\n\nThanks,\n\n-- \nDave Abrahams\nBoostPro Computing\nhttp://www.boostpro.com\n"},{"id":"182233","messageId":"87k44zj0s3.fsf@thomas.inf.ethz.ch","threadId":"29314","inReplyTo":"m239bqnctf.fsf@pluto.luannocracy.com","subject":"Re: [bug] submodule --update insufficiently verbose","fromName":"Thomas Rast","fromEmail":"trast@student.ethz.ch","sentAt":"2012-01-10T10:43:24Z","receivedAt":"2012-01-10T10:43:24Z","isPatch":false,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"Dave Abrahams <dave@boostpro.com> writes:\n\n> When a \"git submodule --update\" fails, e.g., due to a dirty working\n> directory in one of the submodules, nothing is printed out indicating\n> the submodule or directory in which the failure occurred.  This seems\n> like a usability bug to me.\n\nI assume you mean 'git submodule update'.  What git version is this, and\nhow do you reproduce?  I get a message like\n\n  error: Your local changes to the following files would be overwritten by checkout:\n          foo\n  Please, commit your changes or stash them before you can switch branches.\n  Aborting\n  Unable to checkout '1fac3675a8c65b14e0a98e0136b5c43db97706fe' in submodule path 'sub'\n\nin a simple test.  I am using a development version, but a brief glance\nat the history seems to indictate that the 'Unable to ... in submodule\n...' has always been there.\n\n-- \nThomas Rast\ntrast@{inf,student}.ethz.ch\n"}]}