[fossil-users] Commit question

2011-04-04 Thread Tony Perovic
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 last few weeks because I never saw it 
until I upgraded to the latest version of Fossil.

[cid:image002.jpg@01CBF2B5.7E50D4A0]

TONY PEROVIC

tpero...@compumation.commailto:tpero...@compumation.com
www.compumation.com

205 W. Grand Ave., Ste. 121
Bensenville, IL  60106
630-860-1921  Phone
630-860-1928  Fax


inline: image002.jpg___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Commit question

2011-04-04 Thread Richard Hipp
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 question and, more importantly, how do I make it
 stop?


fossil setting crnl-glob *




 This must have been added within the last few weeks because I never saw it
 until I upgraded to the latest version of Fossil.


Added on 2011-02-25




  *TONY PEROVIC*



 tpero...@compumation.com

 www.compumation.com

 205 W. Grand Ave., Ste. 121

 Bensenville, IL  60106

 630-860-1921  Phone

 630-860-1928  Fax



 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




-- 
D. Richard Hipp
d...@sqlite.org
image002.jpg___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Commit question

2011-04-04 Thread Konstantin Khomoutov
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 question and, more importantly, how do I
 make it stop?
http://www.fossil-scm.org/fossil/info/046658848c21cd54749a48bebe7719d62cc9ecef

You will discover another side of this problem when you attempt to do
something like
C:\ fossil diff | gvim -R -
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Commit question

2011-04-04 Thread Tony Perovic
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: fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-users] Commit question


On Mon, Apr 4, 2011 at 11:46 AM, Tony Perovic 
tpero...@compumation.commailto: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 question and, more importantly, how do I make it stop?

fossil setting crnl-glob *


This must have been added within the last few weeks because I never saw it 
until I upgraded to the latest version of Fossil.

Added on 2011-02-25


[cid:image001.jpg@01CBF2BB.0AFB0420]

TONY PEROVIC

tpero...@compumation.commailto:tpero...@compumation.com
www.compumation.comhttp://www.compumation.com

205 W. Grand Ave., Ste. 121
Bensenville, IL  60106
630-860-1921tel:630-860-1921  Phone
630-860-1928tel:630-860-1928  Fax



___
fossil-users mailing list
fossil-users@lists.fossil-scm.orgmailto:fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users



--
D. Richard Hipp
d...@sqlite.orgmailto:d...@sqlite.org
inline: image001.jpg___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] sqlite.org skin

2011-04-04 Thread Wilson, Ronald
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 mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] sqlite.org skin

2011-04-04 Thread Richard Hipp
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 skin sqlite-skin.txt -R sqlite.fossil you'll have the complete
skin-spec in the file sqlite-skin.txt.  You can then import it into
whatever you want using fossil config import sqlite-skin.txt -R
myrepo.fossil.




 RW



 Ron Wilson, Engineering Project Lead

 (o) 434.455.6453, (m) 434.851.1612, www.harris.com



 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Commit question

2011-04-04 Thread sky5walk
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:
 fossil-users-boun...@lists.fossil-scm.org] *On Behalf Of *Richard Hipp
 *Sent:* Monday, April 04, 2011 10:51 AM
 *To:* fossil-users@lists.fossil-scm.org
 *Subject:* Re: [fossil-users] Commit question





 On Mon, Apr 4, 2011 at 11:46 AM, 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 question and, more importantly, how do I make it
 stop?


 fossil setting crnl-glob *




 This must have been added within the last few weeks because I never saw it
 until I upgraded to the latest version of Fossil.


 Added on 2011-02-25




  *TONY PEROVIC*



 tpero...@compumation.com

 www.compumation.com

 205 W. Grand Ave., Ste. 121

 Bensenville, IL  60106

 630-860-1921  Phone

 630-860-1928  Fax




 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




 --
 D. Richard Hipp
 d...@sqlite.org

 ___
 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


Re: [fossil-users] Commit question

2011-04-04 Thread Stephan Beal
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 developers edit a shell script, check it in, release the software, and
then the scripts won't run on the customer's target (Unix) system because
the shell name /bin/sh\r is not recognized as a shell/command. Some
Windows editors can handle and/or emit Unix-style line-ends, but notepad
does not.

On a related note: some tools (like cvs or svn) warn if a file's last line
has no end-of-line marker. That's because (as i was taught, anyway) the
official definition of a text file is basically variable-length records
separated by a record separator (an end-of-line sequence (\n on *nix, \r\n
on Windows)), and that the last record must also have such a separator.

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] Fossil cannot add filenames with \*[]?

2011-04-04 Thread sky5walk
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 the responses came up short.
Any glaring reason(s) for not allowing certain wildcards in filenames?
Especially when competing SCM's are already past this...

I don't use these characters myself, and continue to use Fossil.

-Steve
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Fossil cannot add filenames with \*[]?

2011-04-04 Thread Richard Hipp
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 - [].  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?


The reason such names are disallowed is because they are prone to error.
Not in Fossil itself, but in other software.  For example: optional external
merge and diff programs that people might choose to set up.  So for safety's
sake , Fossil goes to the extra trouble of disallowing them.

Note that it is extra code that checks for these filenames and disallows
them.  This is not a bug.  It is a feature I deliberately introduced and
which I am loath to take out.

But if you really want to disable it, it is simply a matter of commenting
out some code.



 Especially when competing SCM's are already past this...

 I don't use these characters myself, and continue to use Fossil.

 -Steve
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Fossil cannot add filenames with \*[]?

2011-04-04 Thread sky5walk
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 off for want of a file filter. ;)

-Steve

On Mon, Apr 4, 2011 at 5:23 PM, Richard Hipp d...@sqlite.org wrote:


 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 - [].  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?

 The reason such names are disallowed is because they are prone to error.
 Not in Fossil itself, but in other software.  For example: optional external
 merge and diff programs that people might choose to set up.  So for safety's
 sake , Fossil goes to the extra trouble of disallowing them.

 Note that it is extra code that checks for these filenames and disallows
 them.  This is not a bug.  It is a feature I deliberately introduced and
 which I am loath to take out.

 But if you really want to disable it, it is simply a matter of commenting
 out some code.



 Especially when competing SCM's are already past this...

 I don't use these characters myself, and continue to use Fossil.

 -Steve
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users



 --
 D. Richard Hipp
 d...@sqlite.org

 ___
 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


Re: [fossil-users] Fossil cannot add filenames with \*[]?

2011-04-04 Thread Ron Wilson
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 competing SCM's are already past this...

In some development environments, these characters are not a problem.
Only the characters used by the file system, such as / in Unix/Linux
and \ and : in Windows, are not allowed in file names. However, in
environments that, directly or indirectly, use command line
processing, such as shell scripts, .BAT scripts and even make files,
these characters are often used for other purposes and will cause
problems if not properly quoted and/or escaped. That typically adds ',
 and \ to the list of problem characters. Also, ; is often used as a
command delimiter, and the space and tab characters are often used as
parameter delimiters.

As antiquated as it may sound, there as still many tools that assume
these restrictions are in place. (As an FYI. even Windows admins use a
command line environment, especially for custom automated procedures,
which is why Windows still has a command line.)

All that said, however, it would make sense to make the prohibition of
these characters a configurable setting. There are plenty of new
developpers who have never had to worry about these restrictions, so
will likely choose an SCM that either lacks these restrictions or can
be configured to disable them.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users