You can specify whether to ignore the line endings (they're different for
win vs. linux vs. osx, and windows does things oddly...I guess). Open up the
ui ("fossil ui" in an open repository) and then go to the admin, then
"settings". Find the "crnl-glob" setting, and set it to *. This will ignore
all windows CR/NL bad line endings. I don't know how horribly horrible this
is for others, but I have that as a default setting on my computer (win7).Tomek On Wed, May 25, 2011 at 8:28 AM, Gilles <gilles.gana...@free.fr> wrote: > On Wed, 25 May 2011 08:00:01 -0400, Richard Hipp > <d...@sqlite.org> wrote: > >The working directory of the process must be in the checkout. A unix > >program will normally preserve your working directory. But windows is > >different. If you want the command to work, you'll have to find a way to > >make your working directory fall somewhere within your checkout. > > Thanks everyone for the help. Things are clearer now. > > At this point, from a Windows editor, I can successfully add a new > file to a repository after opening it in a DOS box, but I get the > following error when I try to commit: > ============= > C:/SOMEDIR/myfile.txt contains CR/NL line endings; commit anyhow > (yes/no/all)? > C:\fossil.exe: Abandoning commit due to CR+NL line endings in > C:/SOMEDIR/myfile.txt > ============= > > Google didn't return any document about that error: Is there a way to > provide Fossil with an answer to that question, so as not to be > prompted? > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
