Hello,
It would seem there is a bug in update_cmd(). Cloning, syncing and other
operations will call user_select() to setup g.userUid among other
things. This does not happen with update_cmd() so when I'm viewing
/info/artifact through the web UI, it shows ``unknown @ IP'' as the
On Sat, Sep 7, 2013 at 8:51 PM, Andy Bradford <
amb-sendok-1381204277.bfphninpnickkchnj...@bradfords.org> wrote:
> Thus said Matt Welland on Sat, 07 Sep 2013 20:22:42 -0700:
>
> > What is the recommended ssh command line for Linux? 'ssh -q' seems to
> > work fine for me.
>
> I typically don't ch
Thus said Matt Welland on Sat, 07 Sep 2013 20:22:42 -0700:
> What is the recommended ssh command line for Linux? 'ssh -q' seems to
> work fine for me.
I typically don't change the ssh command line unless necessary and the
default of ``ssh -e none -T'' seems to work fine. I haven't seen a
I did a little testing of branch ssh-transport-changes on Ubuntu and they
seem to work well.
What is the recommended ssh command line for Linux? 'ssh -q' seems to work
fine for me.
The -q silences the "pseudo-terminal will not be allocated ... " message.
It might be nice to suppress the echo of t
On 05/09/13 22:41, David Given wrote:
[...]
> I think, without a mathematical proof, that maintaining the ability to
> take prefixes of an encoded name will require us to use a dictionary
> that fits into a precise number of bits. Truncating the dictionary to
> 2^10 entries would be the simplest ap
Hello,
In an effort to simplify the code changes being made, I have separated
out the SSH transport changes from the development of the new (and
somewhat experimental) shared SSH account code. I did this so that it
might be easier to get the more critical SSH transport changes included
On 2013-09-06 20:11, Ross Berteig wrote:
> ba-ba-ba-ba
> 12345678di-ku-poo-wa
> 74a95e62vu-che-roo-si
>
> da39a3ee5e6b4b0d3255bfef95601890afd80709
> ghi-le-clo-phoo-roo-to-no-cy-ki-py-frau-
> phau-bly-sa-fa-bla-chau-gha-bau-ce
I like this, but...
At le
I think the warning should not be there, in the same way there's no warning
when a local non-versioned setting override a global one.
And anyway, when doing 'fossil set' we can see the warning to remind that
the versioned setting exist. Which is useful when looking what the setting
is, the user wi
2013/9/7 Stephan Beal :
> Hi, all,
>
> i don't personally use this feature, but i'm in a repo where versioned
> settings were introduced:
>
> [stephan@host:~/cvs/fossil/libfossil]$ f com -m ...
Yes, after I discovered versioned settings I started
using it, and I like it. Settings like crnl-glob
an
Hi, all,
i don't personally use this feature, but i'm in a repo where versioned
settings were introduced:
[stephan@host:~/cvs/fossil/libfossil]$ f com -m ...
...
Pull finished with 2968 bytes sent, 1907 bytes received
setting crnl-glob has both versioned and non-versioned values: using
versioned
On Sat, Sep 7, 2013 at 10:29 AM, Jan Nijtmans wrote:
> The only difference between the "comment" and the "originComment" is
> the encoding.
> Stephan, your fix appears to work fine.
>
:)
> I think it's ok to display the � character (\ufffd) here, that's
> what firefox does when it encounters in
2013/9/6 Matt Welland :
> fossil: ./src/cson_amalgamation.c:3786: cson_str_to_json: Assertion `*pos ==
> ch' failed.
> "originComment":"Update to Toni RAbort
__
I remember doing that commit, and discovering that when typing the comment
at the prompt on Windows d
12 matches
Mail list logo
