2017-03-15 14:08 GMT+01:00 Jan Nijtmans:
> Please report those things on the SQLite mailing list,
> so it can be properly reviewed and applied upstream.
of course, this should be Fossil mailing list ...
Regards,
Jan Nijtmans
___
2017-03-10 23:41 GMT+01:00 Martin Gagnon:
> It seems to be a problem with a weird filename (with a newline in it),
> added in this checkin:
> http://fossil-scm.org/index.html/info/ac1af2306b70c537
> I have no clue how to fix that.
Looks like Debian has a fix for that:
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
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
On Fri, Mar 10, 2017 at 02:02:23PM -0600, Zakero wrote:
> In an effort to do some experimenting with the latest release of Fossil:
>
> ./fossil-2.1 version
> This is fossil version 2.1 [83e3445f67] 2017-03-10 17:07:08 UT
>
> I wanted to export the fossil repository to git. Then import the "git
In an effort to do some experimenting with the latest release of Fossil:
./fossil-2.1 version
This is fossil version 2.1 [83e3445f67] 2017-03-10 17:07:08 UT
I wanted to export the fossil repository to git. Then import the "git
file" back into fossil. Being the first time to attempt this, there
6 matches
Mail list logo