Max Horn <m...@quendi.de> writes: > So far, all I look at do not deal with this at all. Any attempts > to deal with it should be pretty easy to recognize: The > remote-$backend would have to store something into the git config, > or else, verify the opaque token and refuse to work with it under > certain conditions (e.g. when it contains a relative path). But > they don't. E.g. git-remote-testgit has the exact same problem.
Thanks for confirming what I suspected. I think the way Felipe's patch makes remote-hg take responsibility of how $opaqueToken should look like for future invocations is the simplest and makes the most sense. We could try to go fancier and end up over-engineering, but I'd rather have a simple fix in the tree first. Thanks. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
