Input for monotone automate stdio now has the format
'l'':'[':'...]'e'
, as there were problems mentioned with the previous format. Characters
between the 'e' for one command and the 'l' for the next are ignored
(except for 'l', of course).
Output now has the format
':'':'':'':'
, where cmdnum is
On Mon, 2005-05-23 at 10:17 +0200, Christof Petig wrote:
> Since it uses certificates it should be attack-proof. The ssh branch is
> (in my opinion as the branch coder ;-) ) inferior to port forwarding
> (aka firewall circumventing) via ssh because port forwarding solves
One of my favorite feature
On Mon, May 23, 2005 at 06:37:52PM +0200, Henry Nestler wrote:
> Hello!
>
> The ticker is default "dot". Should default "count"? See --help.
> Older version 0.18 was "--ticker=count" default.
The change is that we taught the Win32 version how to detect whether
it was writing to a terminal or no
Henry Nestler wrote:
> Hello!
>
> The ticker is default "dot". Should default "count"? See --help.
> Older version 0.18 was "--ticker=count" default.
The ticker was changed a while ago to adapt based on the current setting
of TERM. I'm not sure how successful this was on win32 but the basic
ide
On Sat, 21 May 2005 18:40:41 +0800
Matt Johnston <[EMAIL PROTECTED]> wrote:
> On Fri, May 13, 2005 at 09:23:17AM -0700, Mark Wong wrote:
>
> > When I run:
> > monotone --db=markw.db propagate org.osdl.dbt2 org.osdl.test.dbt2
> >
> > and do some manual merging, I get the following, presumably
Hello!
The ticker is default "dot". Should default "count"? See --help.
Older version 0.18 was "--ticker=count" default.
I'm using Win32 EXE, downloaded from homepage. Debug output attached.
>>> monotone --full-version >>>
monotone 0.19 (base revision: ac4b3dd3c60eb95aa18e01d0f525a5dcfa85567c
Nathaniel Smith wrote:
>>static int
>>dump_table_cb(void *data, int n, char **vals, char **cols)
>>{
>>[...]
>> sqlite3_exec_printf(dump->sql, "SELECT * FROM '%q'",
>> dump_row_cb, data, NULL, vals[0]);
>>[...]
>
> Why does this code still call sqlite3_exec_printf?
Nathaniel Smith schrieb:
> It's a little tricky (because it would have to be started from inetd,
> but then take over the listening port while running -- if two people
> connect at the same time, they need to both end up talking to the same
> process, not talking to two different processes). But,
That's handy to know -- I might need to use my repositories on all 3 of
these platforms, soon.
On Sat, 2005-05-21 at 18:19 -0700, Nathaniel Smith wrote:
[...]
> The current policy is:
> -- by default, don't touch line endings at all. In fact, don't
> touch data at all, we store uninterp
Christof Petig schrieb:
>>monotone: fatal: std::logic_error: cvs_client.cc:1465: invariant
>>'I(lresult[0].second=="Clear-static-directory")' violated
>
> I tried and will fix it (today?). CVS server seem to vary greatly when
> it comes to responses ... I tried on all servers I could get my hand o
Bruce Stephens schrieb:
>>- Is the communication during "sync" in some way encrypted?
>
>
> As far as I know, no. I think there's a TLS (or maybe ssh?) branch
> somewhere around, although I don't know how up to date it is.
Since it uses certificates it should be attack-proof. The ssh branch is
(i
On Mon, May 23, 2005 at 09:19:44AM +0200, Christof Petig wrote:
> Nathaniel Smith schrieb:
> > I'm not quite sure what's going on here, but clearly this change makes
> > the code and comment inconsistent. (I guess %-signs are now
> > automatically okay because we no longer go via printf? What if
Nathaniel Smith schrieb:
> Okay, finally had a chance to look at this. Sorry for the delay.
>
> Not sure if these comments are properly directed at you or Derek,
> since it looks like he wrote the original patch. But anyway :-):
>
>
>> // "%s" construction prevents interpretation of %-signs in
13 matches
Mail list logo
