On 23/09/14 00:34, Isarra Yos wrote: For the first one, it may be relevant that all the repositories I've tried so far are submodules, and the .git in those is just a symbolic link to a subdirectory of the .git in the parent repository. I've been dumping the hook in the hooks/ in there.

On 9/23/14, Merlijn van Deen <valhallasw(a)arctus.nl> wrote: Oh cool. I always assumed that access via https password was just totally broken.

On 23/09/14 08:25, Gergo Tisza wrote: My git-review config hasn't changed. Nothing has changed, that I know of, except the version of git-review I have installed. The problems, however, seem to mostly just be with submodules, which is a problem for me because basically everything I do is in submodules. As I understand it, the remotes for the submodules are all set in the parent repository's configuration, and thus will always be the same regardless of how you dowloaded or set up the parent. This is just a guess, mind, but I used ssh to download the extensions repo, the remotes for that are ssh, but the submodule remotes are all https. The weird thing is that apparently git review just used to work with this and automatically translated the submodule remotes depending on what the remotes for the parent were. Now it seems like it's too stupid and I have to manually change all the submodule remotes before I can use them? git review -s also doesn't seem to do anything, so I also have to run a bash script jeremyb sent me (http://paste.debian.net/plain/122534). For every one. Does this seem right? Has anyone else running the current version run into problems with this? Is there any less tedious way to fix this? ...is there any way to downgrade git-review? -I

On 23/09/14 21:13, Gergo Tisza wrote: I did that long ago, before I even installed git-review. Only actually checked what the remotes were now, though. But they won't do ssh unless I specifically tell them. Is git submodule init supposed to be smart enough for that? gerrit is set to use origin, but... Thank you bunches. Switching to git-review 1.21 seems to have fixed it. -I