I can issue this: "wget http://danraymond.org/fossil/mydan.fossil"; and get
the repository file "mydan.fossil"
if I issue: "fossil clone http://danraymond.org/fossil/mydan funny.fossil"
I get:
"server says: 404 Not Found
Clone done, sent: 268 received: 675 ip: 102.0.110.131
server returned an e
On Tue, Mar 14, 2017 at 08:48:50PM -0500, Artur Shepilko wrote:
> Just tried the case of "file name contains a newline char" with git.
> Looks like git encodes such names with C-like characters ('\n' for x0A
> or '\r' for x0D).
>
> Git fast-export outputs such files enquoted as follows:
> M 100644
Just tried the case of "file name contains a newline char" with git.
Looks like git encodes such names with C-like characters ('\n' for x0A
or '\r' for x0D).
Git fast-export outputs such files enquoted as follows:
M 100644 :1 "newline\nfile.txt"
For the same case, fossil export does not encode th
On Wed, Mar 15, 2017 at 1:25 AM, Stephan Beal wrote:
> Yes, it can accept JSON input (even from the CLI). For the full details
> see:
>
> https://docs.google.com/document/d/1fXViveNhDbiXgCuE7QDXQOKeFzf2q
> NUkBEgiUvoqFN4/view
>
> and:
>
> fossil help json
>
> doh - it seems that's missing a refer
On Tue, Mar 14, 2017 at 11:06 PM, Stefan Bellon wrote:
> On Mon, 13 Mar, Ross Berteig wrote:
>
> > When fossil is configured to include JSON support it has a fossil
> > json command that consumes a JSON object full of command and
> > arguments and returns a JSON object of results. A similar featu
On 3/14/2017 3:06 PM, Stefan Bellon wrote:
On Mon, 13 Mar, Ross Berteig wrote:
When fossil is configured to include JSON support it has a fossil
json command that consumes a JSON object full of command and
arguments and returns a JSON object of results. A similar feature is
available over HTTP
On Mon, 13 Mar, Ross Berteig wrote:
> When fossil is configured to include JSON support it has a fossil
> json command that consumes a JSON object full of command and
> arguments and returns a JSON object of results. A similar feature is
> available over HTTP(S) through URLs beginning with /json.
On Mon, 13 Mar, Richard Hipp wrote:
> I'm a little confused. If you need to continue using Fossil 1.29 for
> text output compatibility, then why is it a problem that you cannot
> "fossil update" to the latest trunk? After all, you won't be using
> the latest trunk, right?
Ha, right, that's a li
2017-03-14 16:27 GMT+01:00 Mark Janssen:
> Or in patch form:
...
http://fossil-scm.org/index.html/info/dd41f85acf57290a
Thanks!
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mai
Or in patch form:
@@ -460,15 +460,16 @@
while( i=size ) return 0;
-if( data[i]==c ) return i;
/* not counting escaped chars */
if( i && data[i-1]=='\\' ){
i++;
continue;
}
+
+if( data[i]==c ) return i;
/* skipping a code span */
if( data[i]=='`'
Hello,
on Tuesday 14 March 2017 at 15:44, Mark Janssen wrote:
> I did notice a (IMO) bug during the conversion:
>
> $ cat markdown-test2.md
> _test\_embedded_
> *test\*embedded*
> $ fossil test-markdown-render markdown-test2.md
>
>
> testembedded_
> testembedded*
>
>
>
> The escaped delimite
On Sat, Mar 11, 2017 at 6:18 PM, Natacha Porté wrote:
>
>
> I should really clarify that it was about *fenced* code blocks, since
> traditional markdown code blocks are correctly supported (unless there
> is a serious bug in there).
>
> I do understand the use of code blocks, and use them myself f
12 matches
Mail list logo