Hi,
Stephen Leake wrote:
I think it would be better to store the key in _MTN/options if
--set-default is specified on the 'pull' command line, and then also
use the key from _MTN/options if it is there.
That's easy to implement; I just did it for sync.
Well, that reduces the problem to "o
Markus Schiltknecht <[EMAIL PROTECTED]> writes:
> Jack Lloyd wrote:
>> Wouldn't it make sense though for a pull to (if nothing else) retry
>> using available keys if anonymous access were refused? (Ie, why make
>> the user do it when Monotone can easily guess).
>
> Sure. That has been proposed bef
Quoting Markus Schiltknecht <[EMAIL PROTECTED]>:
Hi,
Jack Lloyd wrote:
Wouldn't it make sense though for a pull to (if nothing else) retry
using available keys if anonymous access were refused? (Ie, why make
the user do it when Monotone can easily guess).
Sure. That has been proposed before,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Markus Schiltknecht schrieb:
> Jack Lloyd wrote:
>> Wouldn't it make sense though for a pull to (if nothing else) retry
>> using available keys if anonymous access were refused? (Ie, why make
>> the user do it when Monotone can easily guess).
>
> Sure
Hi,
Jack Lloyd wrote:
Wouldn't it make sense though for a pull to (if nothing else) retry
using available keys if anonymous access were refused? (Ie, why make
the user do it when Monotone can easily guess).
Sure. That has been proposed before, and we know it would make sense.
However, nobody
On Mon, Mar 31, 2008 at 03:27:35PM +0200, Markus Schiltknecht wrote:
> Hi,
>
> Julio M. Merino Vidal wrote:
> >However, I assumed that 'mtn pull' should do the right thing for any
> >subsequent pull but it does not. It correctly remembers the branch
> >and pattern but it insists on doing anonymou
Hi,
Julio M. Merino Vidal wrote:
However, I assumed that 'mtn pull' should do the right thing for any
subsequent pull but it does not. It correctly remembers the branch
and pattern but it insists on doing anonymous pulls. Should these
secondary pulls also reuse the key used for the initial pul
Hello,
I have configured a Monotone server in which I do not want to allow
anonymous access to certain branches. Everything is working fine
except that "secondary" pulls do not seem to do the right thing. That
is, users first do an initial pull specifying the branch, the pattern
_and_ the key to