Joey Hess a écrit : > It does not support insteadOf at all yet, so is using whatever > remote.origin.url is configured.
Isn't it possible to use 'git remote show origin', which returns the expanded url? > Partly because there is also pushInsteadOf, I'm a bit uncertian what > git-annex should do. Is git-annex a push or a pull? It's neither really. > One way to use insteadOf is to rewrite git+ssh:// to git:// for pulls, > while continuing to use ssh for pushes. In this case, it would seem best > for git-annex to use pushInsteadOf. The same applies for remote.origin.pushurl if it exists, doesn't it? > I suppose if you're using insteadOf to temporarily repoint a repository > to a different server, you won't have a pushInsteadOf, so git-annex > could use the former. Particularly if you're using it to temporarily > switch the domain name used for accessing the same server, that would > be a good use case to support. Yes, that's close to my situation. I actually use insteadOf aliases in my main .gitconfig to specify the hostname of a server which may change in the future (in which case I'll move the data from the old to the new server and then simply adjust the aliases in the main configuration of clients). > However, if that different server has a different git annex on it, > git-annex would think it had stored a file in the old annex, while > really storing it in the insteadOf one. Normally it would not check > that it's seeing the same annex it thought was there. To avoid > this situation, I might try to make git-annex-shell verify the expected > uuid. That's possible, indeed. -- Denis Laxalde -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
