On 08/01/2013 06:56 AM, Matthew Toseland wrote:
> On Wednesday 31 Jul 2013 17:00:50 Arne Babenhauserheide wrote:
>> Am Mittwoch, 31. Juli 2013, 15:50:17 schrieb Matthew Toseland:
>>> Okay. The difficulty here is that there might be more than one
>>> p0s. We should always use the p0s we used last time, for
>>> security's sake. This is probably part of the reason why e.g. git
>>> has a list of remotes for each repository.
>> 
>> You can set explicit paths per repository ([paths] heading in
>> REPO/.hg/hgrc). and IIRC clone does this using the identities USK.
>> So when you clone a repository, the default pull path will always
>> lead to the same repository.
> 
> Right, but what about pulling from a repository other than the
> origin/default? I may regularly review and merge code from a handful
> of other repositories and push it into "my" repository. I need to
> know when I do "git pull operhiem1", or the equivalent hg command, it
> pulls from the same repo as last time.

All of us are proposing things that lead to performing resolution only
once, after which a URI is saved under a constant name. If my
understanding is correct, Mercurial's paths have no equivalent to "git
remote add" - people are intended to edit a configuration file.

How about this: pulling from a WoT repository sets a path with the
resolved URI so the user can use it in the future to refer to the same
identity / repository. It could also be useful to have "hg fn-wot-path".

$ hg fn-wot-path operhiem1/pyProbe # Possible without --wot or similar?
Fetching
USK@pxtehdTmfJwyNUAW2Clk4pwv7Nshyg21NNfXcqzFv4,LTjcTWqvsq3ju6pMGe9Cqb3scvQgECG81hRdgj5WO4s,AQACAAE/vcs/0
Parsing.
Found repository "pyProbe" at
USK@pxtehdTmfJwyNUAW2Clk4pwv7Nshyg21NNfXcqzFv4,LTjcTWqvsq3ju6pMGe9Cqb3scvQgECG81hRdgj5WO4s,AQACAAE/pyProbe.R1/10
Added as path "operhiem1".
$ hg pull operhiem1
Request URI:
USK@pxtehdTmfJwyNUAW2Clk4pwv7Nshyg21NNfXcqzFv4,LTjcTWqvsq3ju6pMGe9Cqb3scvQgECG81hRdgj5WO4s,AQACAAE/pyProbe.R1/10
...

The path's edition would have to be kept up to date, but that's not the
core problem.

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Devl mailing list
[email protected]
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Reply via email to