On 14.01.2013, at 19:14, Junio C Hamano wrote:
Max Horn m...@quendi.de writes:
From: Felipe Contreras felipe.contre...@gmail.com
Mercurial might convert the URL to something more appropriate, like an
absolute path.
What it is converted *TO* is fairly clear with , like an ...,
but
Junio C Hamano gits...@pobox.com writes:
Max Horn m...@quendi.de writes:
...
See also the discussion (yeah, this time a real one ;-) leading to this:
https://github.com/felipec/git/issues/2
...
If I understand correctly, the $backend::$opaqueToken is a contract
between the remote-helper
On 15.01.2013, at 17:05, Junio C Hamano wrote:
Max Horn m...@quendi.de writes:
On 14.01.2013, at 19:14, Junio C Hamano wrote:
What is lacking from this description is why it even needs to work
from a different working directory
In your rewrite below, this is still lacking, I
On 15.01.2013, at 17:51, Junio C Hamano wrote:
Junio C Hamano gits...@pobox.com writes:
Max Horn m...@quendi.de writes:
...
See also the discussion (yeah, this time a real one ;-) leading to this:
https://github.com/felipec/git/issues/2
...
If I understand correctly, the
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
Max Horn m...@quendi.de writes:
From: Felipe Contreras felipe.contre...@gmail.com
Mercurial might convert the URL to something more appropriate, like an
absolute path.
What it is converted *TO* is fairly clear with , like an ...,
but from the first reading it was unclear to me what it is
From: Felipe Contreras felipe.contre...@gmail.com
Mercurial might convert the URL to something more appropriate, like an
absolute path. Lets store that instead of the original URL, which won't
work from a different working directory if it's relative.
Suggested-by: Max Horn m...@quendi.de
7 matches
Mail list logo