Often I will run the following two commands:
fossil add list of files
^add^ci
(i.e., fossil ci list of files) immediately afterwards.
Sometimes I forget the second step and then do some funny stuff (changing
trunks, merging etc.) until I stumble over the uncommitted files.
Is there anything
On 2012-05-23 12:18 , Richard Hipp d...@sqlite.org wrote:
Furthermore, even if you rename libupskirt to something that is
completely benign and inoffensive, it will be difficult to rehabilitate
the code.
Do you mind explaining this bit please, Richard?
TIA,
-Martin
On 2012-05-23 12:39 , Richard Hipp d...@sqlite.org wrote:
On Wed, May 23, 2012 at 12:36 PM, Weber, Martin S
martin.we...@nist.gov wrote:
On 2012-05-23 12:18 , Richard Hipp d...@sqlite.org wrote:
Furthermore, even if you rename libupskirt to something that is
completely benign and inoffensive
On 2012-02-16 12:41 , Thomas Stover c...@thomasstover.com wrote:
I spoke too soon. I get fossil: unknown command: configure on all my
installations. Do I need another build flag?
It's easy actually. The full command is configuration, to which all of
conf, config and even configur are valid
Ross Berteig:
I should be possible to support more than one session cookie per
user, but then you would need a process to occasionally purge
stale sessions from the server. You could do that check on any
session validation, if its been long enough since the last check.
Or at least check a
Right now for the fossil repository itself, I can read write some stuff, but
I cannot read everything. For example, I cannot read the complete list of
users. So the sentence As far as i can see so far, the only ops which _need_
to be authenticated (for purposes of a JSON interface) are
6 matches
Mail list logo
