hoping that this does not generate so much turbelence as the mv/rm issue
did:
I've stumbled over this behavior:
-- there is a user account on a remote repo created for me (with commit
access)
-- I do the clone a la `fossil clone http://myname@URL myrepo.fsl and I'm
asked correctly for the passw
On Thu, Dec 20, 2012 at 11:56 AM, j. van den hoff
wrote:
> I would find it far more intuitive if _after_ a `clone' of the above sort
> (password query for `myname' and all) the corresponding local user would
> be created automagically and also be set to the default user so that I'm
Nothing to do
On Thu, 20 Dec 2012 19:37:35 +0100, Mike Meyer wrote:
On Thu, Dec 20, 2012 at 11:56 AM, j. van den hoff
wrote:
I would find it far more intuitive if _after_ a `clone' of the above
sort
(password query for `myname' and all) the corresponding local user would
be created automagically and also
On Thu, Dec 20, 2012 at 2:11 PM, j. v. d. hoff
wrote:
> On Thu, 20 Dec 2012 19:37:35 +0100, Mike Meyer wrote:
> I'm just proposing to automate what you do manually in the considered
> situation (including chosing a different local password, why not?): create
> the user, make him the default, choo
*stops biting tongue*
To be fair, Git and Mercurial each require you to set a username/email
address in their respective configuration files. If you don't, commits
appear as originating from your login name plus some best-guess attempt
at an email address.
*watches as various folks scramble
5 matches
Mail list logo
