Command: Fossil commit -m Added Test.bat Test.bat
Response: Test.bat contains CR/NL line endings; commit anyhow (y/N/a)?
Of course it does. All Windows text files contain /r/n.
Why is Fossil asking this question and, more importantly, how do I make it stop?
This must have been added within the
On Mon, Apr 4, 2011 at 11:46 AM, Tony Perovic tpero...@compumation.comwrote:
Command: Fossil commit -m Added Test.bat Test.bat
Response: Test.bat contains CR/NL line endings; commit anyhow (y/N/a)?
Of course it does. All Windows text files contain /r/n.
Why is Fossil asking this
On Mon, 4 Apr 2011 10:46:03 -0500
Tony Perovic tpero...@compumation.com wrote:
Command: Fossil commit -m Added Test.bat Test.bat
Response: Test.bat contains CR/NL line endings; commit anyhow (y/N/a)?
Of course it does. All Windows text files contain /r/n.
Why is Fossil asking this
Just curious: why is cr/lf in text files undesirable?
Tony Perovic
Compumation, Inc.
From: fossil-users-boun...@lists.fossil-scm.org
[mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Richard Hipp
Sent: Monday, April 04, 2011 10:51 AM
To:
What skin is the sqlite.org fossil repository using? It is not in the default
skins that come with fossil. Is it published somewhere?
RW
Ron Wilson, Engineering Project Lead
(o) 434.455.6453, (m) 434.851.1612, www.harris.com
___
fossil-users
On Mon, Apr 4, 2011 at 2:52 PM, Wilson, Ronald rwils...@harris.com wrote:
What skin is the sqlite.org fossil repository using? It is not in the
default skins that come with fossil. Is it published somewhere?
Published? If you clone the fossil repository and then do fossil config
export
Thanks!
That was a pain.
On Mon, Apr 4, 2011 at 12:25 PM, Tony Perovic tpero...@compumation.comwrote:
Just curious: why is cr/lf in text files undesirable?
Tony Perovic
Compumation, Inc.
--
*From:* fossil-users-boun...@lists.fossil-scm.org [mailto:
On Mon, Apr 4, 2011 at 6:25 PM, Tony Perovic tpero...@compumation.comwrote:
Just curious: why is cr/lf in text files undesirable?
On *nix systems, the line ending is \n, and having extra newlines in files
can actually break them. i've seen, several times, cases where Windows-based
Java
Hi,
This weekend I was shouting praises of Fossil to a friend in the
release business and he summarily shot me down with a simple attempt
to add his Subversion based repository.
Fossil failed on filenames containing brackets - []. Huh?
Browsing the mail shows this to be a known issue.
Browsing
On Mon, Apr 4, 2011 at 5:11 PM, sky5w...@gmail.com wrote:
Hi,
This weekend I was shouting praises of Fossil to a friend in the
release business and he summarily shot me down with a simple attempt
to add his Subversion based repository.
Fossil failed on filenames containing brackets - [].
Hi,
I looked at the offending files and the brackets as you may have
guessed contained incremental numerals.
something[1].bin, something[2].bin, etc.
Given the filenames are accepted by the O/S, wouldn't it be more
prudent to optionally allow these and other wildcards?
I'm no fan of branching
On Mon, Apr 4, 2011 at 5:11 PM, sky5w...@gmail.com wrote:
Fossil failed on filenames containing brackets - []. Huh?
Browsing the mail shows this to be a known issue.
Browsing the responses came up short.
Any glaring reason(s) for not allowing certain wildcards in filenames?
Especially when
12 matches
Mail list logo
