On Sun, Sep 15, 2013 at 12:56 PM, BohwaZ <[email protected]> wrote:

> provides that, but it's ok as long as it's not turned on by default and
> we can clear the history, like before copying a repository file to
> publish it online.
>

It's stored in the checkout db, so it's _never_ synced. The '-c' flag
clears the history.


> Logging arguments may pose some risk as if you do:
>
> $ fossil remote-url https://bohwaz:[email protected]/


VERY good point. So far that's not implemented, though.


> (yes you can omit the password and fossil will ask you for it, I know)
>
> The password will be logged in cleartext fossil in that case, and that
> may be a problem.
>

Definitely. Thanks for pointing that out. (That said, i've only ever used
the password that way when cloning.)

'cmdhist' seems fine for me, as I would think that 'history' provides
> the history of last checkins, and 'usage' would provide me with some
> help on fossil command line.
>

i agree on all points, i just find cmdhist clumsy to type ;). cmdhist.
Fossil would, however, allow an abbreviation of 'cm', so it wouldn't be
that bad.

-- 
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to