[fossil-users] Commit Question
Typically when I do a commit I simply do : fossil commit From inside the tree of managed artifacts. However, yesterday I realized I was working on 2 different problems and wanted to commit only the single directory tree I was in. I looked up the syntax a realized I could give the commit command a list of files. Question: Is there a way to do a commit on an sub-hierarchy of files e.g. commit from a starting directory? I got the effect I wanted using individual files but it would have been easier to simply supply a directory name such as: fossil commit directory-x Thanks, Tony Jefferson ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] CRLF conversion on windows
Hi, Is there any plan for CRLF conversion under windows? This would be very usefull for cross platform projects. Especially when using Visual Studio on the Windows side, which silently add CRLF line ending on a LF only file which give you a mixed line ending file (got bunch of ^M when editing files with Vim after). it could convert text file from CR-LF to LF when committing and the oposite on checkout, so this would always keep LF line ending on repository and the local checkout on windows would have CR-LF line ending text file. Just like does Git and CVSNT (using Tortoise CVS at least). Of course this might be dangerous for data corruption when some binary file are flag as text file, but this kind of feature would be off by default for sure. -- Martin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] crnl-setting bug
crnl-globA comma-separated list of GLOB patterns for text files in which it is ok to have CR+NL line endings. Set to * to disable CR+NL checking. I'm unable to set crnl-glob to * in windows, per the documentation. I'm using powershell in windows 7 and I've also tried the regular windows command shell. I even tried *.* just for grins. PS C:\rev\src\trader\src fossil settings access-log auto-captcha auto-shun autosync (local) 1 binary-glob clearsign crnl-glob default-perms diff-command dont-push editor gdiff-command gmerge-command https-login ignore-glob (local) *.suo,*.ncb,*/eur_usd*.* http-port localauth(local) 0 main-branch manifest (local) on max-upload mtime-changes pgp-command proxy repo-cksum self-register ssh-command web-browser PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob '*' Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\fossil fossil setting crnl-glob *.* Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil ver This is fossil version [bc427ad727] 2011-04-06 14:31:00 UTC 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] crnl-setting bug
On Thu, 7 Apr 2011 13:37:38 + Wilson, Ronald rwils...@harris.com wrote: crnl-globA comma-separated list of GLOB patterns for text files in which it is ok to have CR+NL line endings. Set to * to disable CR+NL checking. I'm unable to set crnl-glob to * in windows, per the documentation. I'm using powershell in windows 7 and I've also tried the regular windows command shell. I even tried *.* just for grins. PS C:\rev\src\trader\src fossil settings [...] crnl-glob [...] PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob '*' Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\fossil fossil setting crnl-glob *.* Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil ver This is fossil version [bc427ad727] 2011-04-06 14:31:00 UTC What happens if you do this in plain cmd.exe and not in powershell? ___ 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] crnl-setting bug
On Thu, Apr 7, 2011 at 9:37 AM, Wilson, Ronald rwils...@harris.com wrote: crnl-globA comma-separated list of GLOB patterns for text files in which it is ok to have CR+NL line endings. Set to * to disable CR+NL checking. I’m unable to set crnl-glob to * in windows, per the documentation. I’m using powershell in windows 7 and I’ve also tried the regular windows command shell. I even tried *.* just for grins. Apparently, there is no way in the DOS shell to pass * in as a parameter to a program. aside For someone accustomed to working in a luxurious unix environment, trying to get around with a windows shell is a bit like trading in a new BMW or Lexus for a 15-year-old Yugo or Lada. It is a profoundly frustrating experience that tempts one into throwing heavy objects at the screen. No wonder that people raised on windows tend to take a dim view of command-line interfaces. /aside Since the crnl-glob setting will accept a comma-separated list of glob patterns, perhaps you can work around this problem (read: windows bug) as follows: fossil setting crnl-glob *,x PS C:\rev\src\trader\src fossil settings access-log auto-captcha auto-shun autosync (local) 1 binary-glob clearsign crnl-glob default-perms diff-command dont-push editor gdiff-command gmerge-command https-login ignore-glob (local) *.suo,*.ncb,*/eur_usd*.* http-port localauth(local) 0 main-branch manifest (local) on max-upload mtime-changes pgp-command proxy repo-cksum self-register ssh-command web-browser PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob '*' Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\fossil fossil setting crnl-glob *.* Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil ver This is fossil version [bc427ad727] 2011-04-06 14:31:00 UTC 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] CRLF conversion on windows
I'm using fossil version [1d93222627] 2011-03-01 19:04:32 UTC With this version, Fossil warns about CRLF line ends on commit, and allows me to commit anyway, or abort and fix. This is a good option for me. Some files are OK with CRLFs and others are not. I like being able to choose. -Clark - Original Message - From:Martin Gagnon eme...@gmail.com To:Fossil Users Mailing List fossil-users@lists.fossil-scm.org Cc: Sent:Thursday, April 7, 2011 4:11 AM Subject:[fossil-users] CRLF conversion on windows Hi, Is there any plan for CRLF conversion under windows? This would be very usefull for cross platform projects. Especially when using Visual Studio on the Windows side, which silently add CRLF line ending on a LF only file which give you a mixed line ending file (got bunch of ^M when editing files with Vim after). it could convert text file from CR-LF to LF when committing and the oposite on checkout, so this would always keep LF line ending on repository and the local checkout on windows would have CR-LF line ending text file. Just like does Git and CVSNT (using Tortoise CVS at least). Of course this might be dangerous for data corruption when some binary file are flag as text file, but this kind of feature would be off by default for sure. -- Martin ___ 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] crnl-setting bug
You can use fossil ui to set it. Bill On Thu, Apr 7, 2011 at 9:04 AM, Richard Hipp d...@sqlite.org wrote: On Thu, Apr 7, 2011 at 9:37 AM, Wilson, Ronald rwils...@harris.comwrote: crnl-globA comma-separated list of GLOB patterns for text files in which it is ok to have CR+NL line endings. Set to * to disable CR+NL checking. I’m unable to set crnl-glob to * in windows, per the documentation. I’m using powershell in windows 7 and I’ve also tried the regular windows command shell. I even tried *.* just for grins. Apparently, there is no way in the DOS shell to pass * in as a parameter to a program. aside For someone accustomed to working in a luxurious unix environment, trying to get around with a windows shell is a bit like trading in a new BMW or Lexus for a 15-year-old Yugo or Lada. It is a profoundly frustrating experience that tempts one into throwing heavy objects at the screen. No wonder that people raised on windows tend to take a dim view of command-line interfaces. /aside Since the crnl-glob setting will accept a comma-separated list of glob patterns, perhaps you can work around this problem (read: windows bug) as follows: fossil setting crnl-glob *,x PS C:\rev\src\trader\src fossil settings access-log auto-captcha auto-shun autosync (local) 1 binary-glob clearsign crnl-glob default-perms diff-command dont-push editor gdiff-command gmerge-command https-login ignore-glob (local) *.suo,*.ncb,*/eur_usd*.* http-port localauth(local) 0 main-branch manifest (local) on max-upload mtime-changes pgp-command proxy repo-cksum self-register ssh-command web-browser PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob '*' Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\fossil fossil setting crnl-glob *.* Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil ver This is fossil version [bc427ad727] 2011-04-06 14:31:00 UTC 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 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Cloning on IIS
I'm still having trouble cloning/pulling/pushing on Windows/IIS This is my configuration: Anonymous access.in IIS is disabled. Integrated Windows Authentication is enabled. Basic Authentication is enabled. Allow REMOTE_USER authentication is enabled in the repository. If I run Fossil in server mode on my server: Fossil open \Projects\Test\Test.fossil Fossil.server then I can clone the repository like this: Fossil clone http://myserver:8080/ Test.fossil I captured the exchange: Request: POST /xfer/xfer HTTP/1.0 Host: myserver:8080 User-Agent: Fossil/[1d93222627] Content-Type: application/x-fossil Content-Length: 65 65 bytes of binary data Reponse: POST /xfer/xfer HTTP/1.0 Host: myserver:8080 User-Agent: Fossil/[1d93222627] Content-Type: application/x-fossil Content-Length: 267 data packets Since I do not see any login information, I assume that authentication is not required for cloning. If I browse the repository, the browser provides authentication to IIS which, in turn, sets REMOTE_USER=tperovic before invoking Fossil via CGI. The result is auto-login based on Windows integrated authentication. I get Logged on as tperovic on every Fossil web page. Now, if I try to clone the repository using the IIS/CGI interface, it fails: Fossil clone http://myserver/Projects/Test/Test.fossil Test.fossil Request: POST /Projects/Test/Test.fossil/xfer/xfer HTTP/1.0 Host: vserver1 User-Agent: Fossil/[1d93222627] Content-Type: application/x-fossil Content-Length: 63 Media Type: application/x-fossil (63 bytes) Reponse: HTTP/1.1 401 Unauthorized Content-Length: 1539 Content-Type: text/html Server: Microsoft-IIS/6.0 WWW-Authenticate: Negotiate WWW-Authenticate: NTLM WWW-Authenticate: Basic realm=My Domain Date: Fri, 01 Apr 2011 18:05:16 GMT Connection: close HTMLHEADTITLEYou are not authorized to view this page/TITLE ... .h2HTTP Error 401.2 - Unauthorized: Access is denied due to server configuration.brInternet Information Services (IIS)/h2 ... /HTML Normally, the browser would negotiate the authentication method with IIS. The WWW-Authenticate directives tell the browser which authentication methods are available. Fossil provides no authentication so IIS rejects the request . Thus, I conlude, anonymous access must to be enabled for cloning to work. I would imagine you would have the same issue on Unix/Linux. Is this correct? [cid:image001.jpg@01CBF508.D3E254C0] 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: image001.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] crnl-setting bug
On Thu, Apr 7, 2011 at 10:46 AM, Bill Burdick bill.burd...@gmail.comwrote: You can use fossil ui to set it. Excellent suggestion, Bill. That is my new preferred solution. Please ignore my prior hack. Bill On Thu, Apr 7, 2011 at 9:04 AM, Richard Hipp d...@sqlite.org wrote: On Thu, Apr 7, 2011 at 9:37 AM, Wilson, Ronald rwils...@harris.comwrote: crnl-globA comma-separated list of GLOB patterns for text files in which it is ok to have CR+NL line endings. Set to * to disable CR+NL checking. I’m unable to set crnl-glob to * in windows, per the documentation. I’m using powershell in windows 7 and I’ve also tried the regular windows command shell. I even tried *.* just for grins. Apparently, there is no way in the DOS shell to pass * in as a parameter to a program. aside For someone accustomed to working in a luxurious unix environment, trying to get around with a windows shell is a bit like trading in a new BMW or Lexus for a 15-year-old Yugo or Lada. It is a profoundly frustrating experience that tempts one into throwing heavy objects at the screen. No wonder that people raised on windows tend to take a dim view of command-line interfaces. /aside Since the crnl-glob setting will accept a comma-separated list of glob patterns, perhaps you can work around this problem (read: windows bug) as follows: fossil setting crnl-glob *,x PS C:\rev\src\trader\src fossil settings access-log auto-captcha auto-shun autosync (local) 1 binary-glob clearsign crnl-glob default-perms diff-command dont-push editor gdiff-command gmerge-command https-login ignore-glob (local) *.suo,*.ncb,*/eur_usd*.* http-port localauth(local) 0 main-branch manifest (local) on max-upload mtime-changes pgp-command proxy repo-cksum self-register ssh-command web-browser PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob '*' Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\fossil fossil setting crnl-glob *.* Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil ver This is fossil version [bc427ad727] 2011-04-06 14:31:00 UTC 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 -- 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] Cloning on IIS
On Thu, Apr 7, 2011 at 10:48 AM, Tony Perovic tpero...@compumation.comwrote: I’m still having trouble cloning/pulling/pushing on Windows/IIS…. This is my configuration: Anonymous access.in IIS is disabled. Integrated Windows Authentication is enabled. Basic Authentication is enabled. Allow REMOTE_USER authentication is enabled in the repository. Yeah. The Fossil clone client-side still doesn't know how to do Basic Authentication. Somebody posted a patch to fix this a week or two ago. I was going to look into that, but I it just hasn't come up on my queue yet. If I run Fossil in server mode on my server: Fossil open \Projects\Test\Test.fossil Fossil.server then I can clone the repository like this: Fossil clone http://myserver:8080/ Test.fossil I captured the exchange: Request: POST /xfer/xfer HTTP/1.0 Host: myserver:8080 User-Agent: Fossil/[1d93222627] Content-Type: application/x-fossil Content-Length: 65 65 bytes of binary data Reponse: POST /xfer/xfer HTTP/1.0 Host: myserver:8080 User-Agent: Fossil/[1d93222627] Content-Type: application/x-fossil Content-Length: 267 data packets Since I do not see any login information, I assume that authentication is not required for cloning. If I browse the repository, the browser provides authentication to IIS which, in turn, sets REMOTE_USER=tperovic before invoking Fossil via CGI. The result is auto-login based on Windows integrated authentication. I get “Logged on as tperovic” on every Fossil web page. Now, if I try to clone the repository using the IIS/CGI interface, it fails: Fossil clone http://myserver/Projects/Test/Test.fossil Test.fossil Request: POST /Projects/Test/Test.fossil/xfer/xfer HTTP/1.0 Host: vserver1 User-Agent: Fossil/[1d93222627] Content-Type: application/x-fossil Content-Length: 63 Media Type: application/x-fossil (63 bytes) Reponse: HTTP/1.1 401 Unauthorized Content-Length: 1539 Content-Type: text/html Server: Microsoft-IIS/6.0 WWW-Authenticate: Negotiate WWW-Authenticate: NTLM WWW-Authenticate: Basic realm=My Domain Date: Fri, 01 Apr 2011 18:05:16 GMT Connection: close HTMLHEADTITLEYou are not authorized to view this page/TITLE … .h2HTTP Error 401.2 - Unauthorized: Access is denied due to server configuration.brInternet Information Services (IIS)/h2 … /HTML Normally, the browser would negotiate the authentication method with IIS. The WWW-Authenticate directives tell the browser which authentication methods are available. Fossil provides no authentication so IIS rejects the request . Thus, I conlude, anonymous access must to be enabled for cloning to work. I would imagine you would have the same issue on Unix/Linux. Is this correct? *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 image001.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] Cloning on IIS
So, is anonymous access required for cloning even on Unix/Linux? 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: Thursday, April 07, 2011 9:54 AM To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] Cloning on IIS On Thu, Apr 7, 2011 at 10:48 AM, Tony Perovic tpero...@compumation.commailto:tpero...@compumation.com wrote: I'm still having trouble cloning/pulling/pushing on Windows/IIS This is my configuration: Anonymous access.inhttp://access.in IIS is disabled. Integrated Windows Authentication is enabled. Basic Authentication is enabled. Allow REMOTE_USER authentication is enabled in the repository. Yeah. The Fossil clone client-side still doesn't know how to do Basic Authentication. Somebody posted a patch to fix this a week or two ago. I was going to look into that, but I it just hasn't come up on my queue yet. If I run Fossil in server mode on my server: Fossil open \Projects\Test\Test.fossil Fossil.server then I can clone the repository like this: Fossil clone http://myserver:8080/ Test.fossil I captured the exchange: Request: POST /xfer/xfer HTTP/1.0 Host: myserver:8080 User-Agent: Fossil/[1d93222627] Content-Type: application/x-fossil Content-Length: 65 65 bytes of binary data Reponse: POST /xfer/xfer HTTP/1.0 Host: myserver:8080 User-Agent: Fossil/[1d93222627] Content-Type: application/x-fossil Content-Length: 267 data packets Since I do not see any login information, I assume that authentication is not required for cloning. If I browse the repository, the browser provides authentication to IIS which, in turn, sets REMOTE_USER=tperovic before invoking Fossil via CGI. The result is auto-login based on Windows integrated authentication. I get Logged on as tperovic on every Fossil web page. Now, if I try to clone the repository using the IIS/CGI interface, it fails: Fossil clone http://myserver/Projects/Test/Test.fossil Test.fossil Request: POST /Projects/Test/Test.fossil/xfer/xfer HTTP/1.0 Host: vserver1 User-Agent: Fossil/[1d93222627] Content-Type: application/x-fossil Content-Length: 63 Media Type: application/x-fossil (63 bytes) Reponse: HTTP/1.1 401 Unauthorized Content-Length: 1539 Content-Type: text/html Server: Microsoft-IIS/6.0 WWW-Authenticate: Negotiate WWW-Authenticate: NTLM WWW-Authenticate: Basic realm=My Domain Date: Fri, 01 Apr 2011 18:05:16 GMT Connection: close HTMLHEADTITLEYou are not authorized to view this page/TITLE ... .h2HTTP Error 401.2 - Unauthorized: Access is denied due to server configuration.brInternet Information Services (IIS)/h2 ... /HTML Normally, the browser would negotiate the authentication method with IIS. The WWW-Authenticate directives tell the browser which authentication methods are available. Fossil provides no authentication so IIS rejects the request . Thus, I conlude, anonymous access must to be enabled for cloning to work. I would imagine you would have the same issue on Unix/Linux. Is this correct? [cid:image001.jpg@01CBF50B.080CE7E0] 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
Re: [fossil-users] crnl-setting bug
On Thu, 7 Apr 2011 10:04:22 -0400 Richard Hipp d...@sqlite.org wrote: On Thu, Apr 7, 2011 at 9:37 AM, Wilson, Ronald rwils...@harris.com wrote: crnl-globA comma-separated list of GLOB patterns for text files in which it is ok to have CR+NL line endings. Set to * to disable CR+NL checking. I’m unable to set crnl-glob to * in windows, per the documentation. I’m using powershell in windows 7 and I’ve also tried the regular windows command shell. I even tried *.* just for grins. Apparently, there is no way in the DOS shell to pass * in as a parameter to a program. I think you're wrong. To demonstrate (Windows XP, cmd.exe): C:\fossil set crnl-glob C:\fossil settings|grep crnl crnl-glob(local) C:\fossil set crnl-glob * C:\fossil settings|grep crnl crnl-glob(local) * [...] In fact, cmd.exe has the opposite problem: while on Unix it expands bare * in certain places, trying to replace it with a matching list of files, on Windows the shell passes the asterisk to the program it calls as is and the program is then supposed to do whatever it wants with that asterisk. I mean that in a POSIX shell, if we have $ ls aaa bbb ccc then $ rm * will result in the call rm aaa bbb ccc, while on Windows it will result in the call rm *. On the other hand, the original poster seems to be using PowerShell, not cmd.exe; I'm personally not familiar with it (our shop is still using Windows XP/Windows 2003 on which PowerShell is painfully slow to the level of being unusable) and it might well have different semantics. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] tags branches after importing from CVS
Hi, I've imported a CVS repository, and git-cvsimport converted the HEAD CVS branch to a master one. Since fossil uses trunk as it's default branch, I've tried to rename all master tags/properties to trunk. It has kind-of-worked with awk + xargs, but I forgot the --propagate, so now I'm trying to get a my last check-in set up so I can start working (and fossil checkout gives me my latest code by default) Various combinations of tag add tag cancel have ended up with (mispellings and all): jpicanyol@jpicanyol-desktop:~/wd$ fossil tag list --raw c57a6c30e7 branch=master branck branck=trunk sym-branck=trunk sym-sym-sym-trunk sym-sym-trunk sym-trunk trunk jpicanyol@jpicanyol-desktop:~/wd$ fossil tag list c57a6c30e7 I'm not quite sure on the meaning of all of these, and I'm not even sure how I'd want them to be. Some clues please? How is tag cancel supposed to work and how am I supposed verify it? Where are the magic tags modified by --raw defined? tks -- pica p.s.: regarding the wiki-shed, I'd vote for extending the current synta to allow sub-nesting of lists some simple heading support. ___ 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] crnl-setting bug
PS C:\Users\rwilso20 cmd Microsoft Windows [Version 6.0.6002] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\Users\rwilso20cd \rev\src\fossil C:\rev\src\fossilfossil setting crnl-glob * Usage: C:\rev\src\fossil\fossil.exe setting ?PROPERTY? ?VALUE? RW Ron Wilson, Engineering Project Lead (o) 434.455.6453, (m) 434.851.1612, www.harris.com HARRIS CORPORATION | RF Communications Division assuredcommunications™ -Original Message- From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users- boun...@lists.fossil-scm.org] On Behalf Of Konstantin Khomoutov Sent: Thursday, April 07, 2011 11:25 AM To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] crnl-setting bug On Thu, 7 Apr 2011 10:04:22 -0400 Richard Hipp d...@sqlite.org wrote: On Thu, Apr 7, 2011 at 9:37 AM, Wilson, Ronald rwils...@harris.com wrote: crnl-globA comma-separated list of GLOB patterns for text files in which it is ok to have CR+NL line endings. Set to * to disable CR+NL checking. I’m unable to set crnl-glob to * in windows, per the documentation. I’m using powershell in windows 7 and I’ve also tried the regular windows command shell. I even tried *.* just for grins. Apparently, there is no way in the DOS shell to pass * in as a parameter to a program. I think you're wrong. To demonstrate (Windows XP, cmd.exe): C:\fossil set crnl-glob C:\fossil settings|grep crnl crnl-glob(local) C:\fossil set crnl-glob * C:\fossil settings|grep crnl crnl-glob(local) * [...] In fact, cmd.exe has the opposite problem: while on Unix it expands bare * in certain places, trying to replace it with a matching list of files, on Windows the shell passes the asterisk to the program it calls as is and the program is then supposed to do whatever it wants with that asterisk. I mean that in a POSIX shell, if we have $ ls aaa bbb ccc then $ rm * will result in the call rm aaa bbb ccc, while on Windows it will result in the call rm *. On the other hand, the original poster seems to be using PowerShell, not cmd.exe; I'm personally not familiar with it (our shop is still using Windows XP/Windows 2003 on which PowerShell is painfully slow to the level of being unusable) and it might well have different semantics. ___ 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] Personal wiki hack for synapse/gnome-do/quicksilver/etc.
So, the point of that command is to make an xterm that you can kill to stop your fossil ui, so you don't stack up 10 fossil ui commands. In windows, you can use Launchy for this (similar to gnome-do, quicksilver, etc.). Here's an improved script that doesn't depend on nc. Windows users should be able to convert this to a batch file that uses cmd \K (I think that's the right option) instead of xterm: #!/bin/sh cd $HOME/Notes/fossil-wiki xterm -e fossil ui -P || google-chrome localhost: Bill On Thu, Apr 7, 2011 at 10:18 AM, Bill Burdick bill.burd...@gmail.comwrote: Every now and then I review my need for personal wiki. I use Tiddlywiki for a lot of things, but it's not version controlled (out of the box) and I've also used Ikiwiki, which is really neat. Yesterday I had a duh moment when I realized I can use Fossil for this, but I wanted a nice way to start it from Synapse by just typing wiki, so I made this script. Maybe some other people will find it helpful (I set the Fossil server port to )... #!/bin/sh if nc -z localhost then exec google-chrome localhost: else cd $HOME/Notes/fossil-wiki exec xterm -e fossil ui fi Bill ___ 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] tags branches after importing from CVS
One thing you can do is use fossil ui to view the timeline, see the branch diagram, and edit tag names. Bill On Thu, Apr 7, 2011 at 10:28 AM, Joan Picanyol i Puig lists-fos...@biaix.org wrote: Hi, I've imported a CVS repository, and git-cvsimport converted the HEAD CVS branch to a master one. Since fossil uses trunk as it's default branch, I've tried to rename all master tags/properties to trunk. It has kind-of-worked with awk + xargs, but I forgot the --propagate, so now I'm trying to get a my last check-in set up so I can start working (and fossil checkout gives me my latest code by default) Various combinations of tag add tag cancel have ended up with (mispellings and all): jpicanyol@jpicanyol-desktop:~/wd$ fossil tag list --raw c57a6c30e7 branch=master branck branck=trunk sym-branck=trunk sym-sym-sym-trunk sym-sym-trunk sym-trunk trunk jpicanyol@jpicanyol-desktop:~/wd$ fossil tag list c57a6c30e7 I'm not quite sure on the meaning of all of these, and I'm not even sure how I'd want them to be. Some clues please? How is tag cancel supposed to work and how am I supposed verify it? Where are the magic tags modified by --raw defined? tks -- pica p.s.: regarding the wiki-shed, I'd vote for extending the current synta to allow sub-nesting of lists some simple heading support. ___ 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] CRLF conversion on windows
I know this new feature. But I'm really talking about converting the line ending, for cross platform development issue. -- Martin Le 2011-04-07 à 10:43, Clark Christensen cdcmi...@yahoo.com a écrit : I'm using fossil version [1d93222627] 2011-03-01 19:04:32 UTC With this version, Fossil warns about CRLF line ends on commit, and allows me to commit anyway, or abort and fix. This is a good option for me. Some files are OK with CRLFs and others are not. I like being able to choose. -Clark - Original Message - From:Martin Gagnon eme...@gmail.com To:Fossil Users Mailing List fossil-users@lists.fossil-scm.org Cc: Sent:Thursday, April 7, 2011 4:11 AM Subject:[fossil-users] CRLF conversion on windows Hi, Is there any plan for CRLF conversion under windows? This would be very usefull for cross platform projects. Especially when using Visual Studio on the Windows side, which silently add CRLF line ending on a LF only file which give you a mixed line ending file (got bunch of ^M when editing files with Vim after). it could convert text file from CR-LF to LF when committing and the oposite on checkout, so this would always keep LF line ending on repository and the local checkout on windows would have CR-LF line ending text file. Just like does Git and CVSNT (using Tortoise CVS at least). Of course this might be dangerous for data corruption when some binary file are flag as text file, but this kind of feature would be off by default for sure. -- Martin ___ 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 ___ 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] tags branches after importing from CVS
Uhm, Via the ui I just saw: branch cancelled by [7020f3fb3d] on 2011-04-07 15:32:07 branck cancelled by [200825f86c] on 2011-04-07 15:32:29 branck=trunk cancelled by [0f89bfc5b1] on 2011-04-07 15:26:16 brank cancelled by [f86c8555bd] on 2011-04-07 15:32:20 sym-branck=trunk cancelled by [c1d92a38da] on 2011-04-07 15:26:00 sym-sym-sym-trunk cancelled by [a75d3427b1] on 2011-04-07 15:24:34 sym-sym-trunk cancelled by [5ef7ad5557] on 2011-04-07 15:25:38 sym-trunk cancelled by [60206e9e0d] on 2011-04-07 15:25:21 trunk cancelled by [58019747433c] on 2011-04-07 15:25:09 Which are my messy attempts to clean up. So, what should I put at the Add the following new tag name to this check-in: and Make this check-in the start of a new branch named: to get later checkings I've done unto the trunk branch? Also, how do I make the changes propagating ? tks -- pica * Bill Burdick bill.burd...@gmail.com [20110407 17:45]: One thing you can do is use fossil ui to view the timeline, see the branch diagram, and edit tag names. Bill On Thu, Apr 7, 2011 at 10:28 AM, Joan Picanyol i Puig lists-fos...@biaix.org wrote: Hi, I've imported a CVS repository, and git-cvsimport converted the HEAD CVS branch to a master one. Since fossil uses trunk as it's default branch, I've tried to rename all master tags/properties to trunk. It has kind-of-worked with awk + xargs, but I forgot the --propagate, so now I'm trying to get a my last check-in set up so I can start working (and fossil checkout gives me my latest code by default) Various combinations of tag add tag cancel have ended up with (mispellings and all): jpicanyol@jpicanyol-desktop:~/wd$ fossil tag list --raw c57a6c30e7 branch=master branck branck=trunk sym-branck=trunk sym-sym-sym-trunk sym-sym-trunk sym-trunk trunk jpicanyol@jpicanyol-desktop:~/wd$ fossil tag list c57a6c30e7 I'm not quite sure on the meaning of all of these, and I'm not even sure how I'd want them to be. Some clues please? How is tag cancel supposed to work and how am I supposed verify it? Where are the magic tags modified by --raw defined? tks -- pica p.s.: regarding the wiki-shed, I'd vote for extending the current synta to allow sub-nesting of lists some simple heading support. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- pica ___ 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] crnl-setting bug
On Thu, 7 Apr 2011 15:44:12 + Wilson, Ronald rwils...@harris.com wrote: PS C:\Users\rwilso20 cmd Microsoft Windows [Version 6.0.6002] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\Users\rwilso20cd \rev\src\fossil C:\rev\src\fossilfossil setting crnl-glob * Usage: C:\rev\src\fossil\fossil.exe setting ?PROPERTY? ?VALUE? Then this might really be a bug as I'm using an older version (currently available at the downloads page): This is fossil version [84e755e213] 2011-03-16 11:19:14 UTC I failed to build the current trunk so can't really tell if it fails for me or not. Will try to fix the build system and proceed. ___ 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] crnl-setting bug
I prefer an automated approach. (assuming the batch file is simpler than sending data to the ui) The fossil settings work for me on XPsp3. C:\fossilcmd Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\fossilfossil setting crnl-glob * C:\fossil -Steve On Thu, Apr 7, 2011 at 10:46 AM, Bill Burdick bill.burd...@gmail.com wrote: You can use fossil ui to set it. Bill On Thu, Apr 7, 2011 at 9:04 AM, Richard Hipp d...@sqlite.org wrote: On Thu, Apr 7, 2011 at 9:37 AM, Wilson, Ronald rwils...@harris.com wrote: crnl-glob A comma-separated list of GLOB patterns for text files in which it is ok to have CR+NL line endings. Set to * to disable CR+NL checking. I’m unable to set crnl-glob to * in windows, per the documentation. I’m using powershell in windows 7 and I’ve also tried the regular windows command shell. I even tried *.* just for grins. Apparently, there is no way in the DOS shell to pass * in as a parameter to a program. aside For someone accustomed to working in a luxurious unix environment, trying to get around with a windows shell is a bit like trading in a new BMW or Lexus for a 15-year-old Yugo or Lada. It is a profoundly frustrating experience that tempts one into throwing heavy objects at the screen. No wonder that people raised on windows tend to take a dim view of command-line interfaces. /aside Since the crnl-glob setting will accept a comma-separated list of glob patterns, perhaps you can work around this problem (read: windows bug) as follows: fossil setting crnl-glob *,x PS C:\rev\src\trader\src fossil settings access-log auto-captcha auto-shun autosync (local) 1 binary-glob clearsign crnl-glob default-perms diff-command dont-push editor gdiff-command gmerge-command https-login ignore-glob (local) *.suo,*.ncb,*/eur_usd*.* http-port localauth (local) 0 main-branch manifest (local) on max-upload mtime-changes pgp-command proxy repo-cksum self-register ssh-command web-browser PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob '*' Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\fossil fossil setting crnl-glob *.* Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil ver This is fossil version [bc427ad727] 2011-04-06 14:31:00 UTC 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 ___ 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] crnl-setting bug
It seems that Vista and Windows 7 don't support sending * as an argument. For XP, apparently it works. Bill On Thu, Apr 7, 2011 at 10:58 AM, sky5w...@gmail.com wrote: I prefer an automated approach. (assuming the batch file is simpler than sending data to the ui) The fossil settings work for me on XPsp3. C:\fossilcmd Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\fossilfossil setting crnl-glob * C:\fossil -Steve On Thu, Apr 7, 2011 at 10:46 AM, Bill Burdick bill.burd...@gmail.com wrote: You can use fossil ui to set it. Bill On Thu, Apr 7, 2011 at 9:04 AM, Richard Hipp d...@sqlite.org wrote: On Thu, Apr 7, 2011 at 9:37 AM, Wilson, Ronald rwils...@harris.com wrote: crnl-globA comma-separated list of GLOB patterns for text files in which it is ok to have CR+NL line endings. Set to * to disable CR+NL checking. I’m unable to set crnl-glob to * in windows, per the documentation. I’m using powershell in windows 7 and I’ve also tried the regular windows command shell. I even tried *.* just for grins. Apparently, there is no way in the DOS shell to pass * in as a parameter to a program. aside For someone accustomed to working in a luxurious unix environment, trying to get around with a windows shell is a bit like trading in a new BMW or Lexus for a 15-year-old Yugo or Lada. It is a profoundly frustrating experience that tempts one into throwing heavy objects at the screen. No wonder that people raised on windows tend to take a dim view of command-line interfaces. /aside Since the crnl-glob setting will accept a comma-separated list of glob patterns, perhaps you can work around this problem (read: windows bug) as follows: fossil setting crnl-glob *,x PS C:\rev\src\trader\src fossil settings access-log auto-captcha auto-shun autosync (local) 1 binary-glob clearsign crnl-glob default-perms diff-command dont-push editor gdiff-command gmerge-command https-login ignore-glob (local) *.suo,*.ncb,*/eur_usd*.* http-port localauth(local) 0 main-branch manifest (local) on max-upload mtime-changes pgp-command proxy repo-cksum self-register ssh-command web-browser PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob * Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil setting crnl-glob '*' Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\fossil fossil setting crnl-glob *.* Usage: c:\rev\bin\fossil.exe setting ?PROPERTY? ?VALUE? PS C:\rev\src\trader\src fossil ver This is fossil version [bc427ad727] 2011-04-06 14:31:00 UTC 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 ___ 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 ___ 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] crnl-setting bug
Whoa! How do you... c:\tempdel *.* Some Dot.Net framework class is required? ___ 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] crnl-setting bug
Apparently the Vista and Windows 7 shell does the file matching and sends the matched files to the command, rather than sending *.*' to the command and having the command do the matching, somewhat like how shells work in UNIX. Bill On Thu, Apr 7, 2011 at 11:18 AM, sky5w...@gmail.com wrote: Whoa! How do you... c:\tempdel *.* Some Dot.Net framework class is required? ___ 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] lol ... mildly humorous fossil usage error...
Here's what I did in a script that had the same problem: unset PATH_INFO SCRIPT_NAME REQUEST_URI SERVER_PROTOCOL REQUEST_METHOD QUERY_STRING STATUS PATH_TRANSLATED SCRIPT_URI SCRIPT_URL GATEWAY_INTERFACE SERVER_NAME DOCUMENT_ROOT Bill On Wed, Apr 6, 2011 at 8:22 PM, Ron Wilson ronw.m...@gmail.com wrote: On Wed, Apr 6, 2011 at 7:53 PM, Stephan Beal sgb...@googlemail.com wrote: The problem turned out to be... i'm developing a CGI framework and to facilitate testing i've defined a few CGI-defined environment variables into my shell session. Fossil saw those and assumed he was in CGI mode, but then didn't have enough info to do anything. The lesson being, don't tell fossil that your interactive shell is a CGI environment. Maybe if you define your command alias to either give empty values or unset those environment variables, you would avoid this. ___ 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] CRLF conversion on windows
On Thu, 7 Apr 2011 12:04:44 -0400 sky5w...@gmail.com wrote: I would be immensely confused if my SCM was modifying the contents of my source code and/or support documents. Given that MacOS has yet another EOL = [CR], it is better for your own code to manage distribution effects. I think it's no longer true: CR was used on prehistoric Macs (those from eighties); contemporary Macs are quite POSIX'y and have LF as a conventional line-ending marker. As to imaginable hassles of auto-conversions, I think this is an exaggregation: Subversion and Git do this for ages and there's no apparent complaints about how they do this. In case you're interested, here are explanations on how they do this: http://svnbook.red-bean.com/en/1.5/svn.advanced.props.file-portability.html#svn.advanced.props.special.eol-style http://www.kernel.org/pub/software/scm/git/docs/git-config.html (see core.eol, core.safecrlf, core.autocrlf; Git for Windows has core.autocrlf set to true by default). ___ 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] CRLF conversion on windows
MacOSX is using UNIX line ending since more than 10 years-ago. In modern computers, there are two options: Unix/MacOSX: LF Windows: CR-LF I would not see it as a problem that fossil changed line-endings if it was disabled by default and it could be enabled with something similar to: fossil setting ascii-glob *.c,*.h Another thing that would be a bonus for cross-platform development would be to change the encoding of the text files. In modern Linux it is utf-8. And in modern Windows, it is a code page that depends on the country but it is different from utf-8 I understand that it is more reasonable to implement in a SCM only the line-ending change, but I wanted to write the encoding problem just for the record. Regards RR 2011/4/7 sky5w...@gmail.com: I would be immensely confused if my SCM was modifying the contents of my source code and/or support documents. Given that MacOS has yet another EOL = [CR], it is better for your own code to manage distribution effects. Just my opinion. -Steve On Thu, Apr 7, 2011 at 11:54 AM, Martin Gagnon eme...@gmail.com wrote: I know this new feature. But I'm really talking about converting the line ending, for cross platform development issue. -- Martin Le 2011-04-07 à 10:43, Clark Christensen cdcmi...@yahoo.com a écrit : I'm using fossil version [1d93222627] 2011-03-01 19:04:32 UTC With this version, Fossil warns about CRLF line ends on commit, and allows me to commit anyway, or abort and fix. This is a good option for me. Some files are OK with CRLFs and others are not. I like being able to choose. -Clark - Original Message - From:Martin Gagnon eme...@gmail.com To:Fossil Users Mailing List fossil-users@lists.fossil-scm.org Cc: Sent:Thursday, April 7, 2011 4:11 AM Subject:[fossil-users] CRLF conversion on windows Hi, Is there any plan for CRLF conversion under windows? This would be very usefull for cross platform projects. Especially when using Visual Studio on the Windows side, which silently add CRLF line ending on a LF only file which give you a mixed line ending file (got bunch of ^M when editing files with Vim after). it could convert text file from CR-LF to LF when committing and the oposite on checkout, so this would always keep LF line ending on repository and the local checkout on windows would have CR-LF line ending text file. Just like does Git and CVSNT (using Tortoise CVS at least). Of course this might be dangerous for data corruption when some binary file are flag as text file, but this kind of feature would be off by default for sure. -- Martin ___ 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 ___ 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 ___ 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] crnl-setting bug
On Thu, 7 Apr 2011 15:44:12 + Wilson, Ronald rwils...@harris.com wrote: PS C:\Users\rwilso20 cmd Microsoft Windows [Version 6.0.6002] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\Users\rwilso20cd \rev\src\fossil C:\rev\src\fossilfossil setting crnl-glob * Usage: C:\rev\src\fossil\fossil.exe setting ?PROPERTY? ?VALUE? I asked a fellow user of Windows 7 to test the version available from the downloads page (which I used under Windows XP) and he confirms the problem you're seeing. ___ 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] CRLF conversion on windows
On Thu, Apr 7, 2011 at 12:42 PM, Ramon Ribó ram...@compassis.com wrote: MacOSX is using UNIX line ending since more than 10 years-ago. In modern computers, there are two options: Unix/MacOSX: LF Also, Solaris, AIX, HPUX, NetBSD, OpenBSD, QNX, etc. Windows: CR-LF The odd man out. I would not see it as a problem that fossil changed line-endings if it was disabled by default and it could be enabled with something similar to: fossil setting ascii-glob *.c,*.h Another thing that would be a bonus for cross-platform development would be to change the encoding of the text files. In modern Linux it is utf-8. And in modern Windows, it is a code page that depends on the country but it is different from utf-8 Notice how everybody else uses utf8 for everything. Only on windows do we have issues with locale-dependent code pages. There are countless operating systems available today, each with is own peccadillos. So why is it always windows that gives trouble? The more one tries to make code cross-platform, the more one realizes that windows is the problem child. I understand that it is more reasonable to implement in a SCM only the line-ending change, but I wanted to write the encoding problem just for the record. Regards RR 2011/4/7 sky5w...@gmail.com: I would be immensely confused if my SCM was modifying the contents of my source code and/or support documents. Given that MacOS has yet another EOL = [CR], it is better for your own code to manage distribution effects. Just my opinion. -Steve On Thu, Apr 7, 2011 at 11:54 AM, Martin Gagnon eme...@gmail.com wrote: I know this new feature. But I'm really talking about converting the line ending, for cross platform development issue. -- Martin Le 2011-04-07 à 10:43, Clark Christensen cdcmi...@yahoo.com a écrit : I'm using fossil version [1d93222627] 2011-03-01 19:04:32 UTC With this version, Fossil warns about CRLF line ends on commit, and allows me to commit anyway, or abort and fix. This is a good option for me. Some files are OK with CRLFs and others are not. I like being able to choose. -Clark - Original Message - From:Martin Gagnon eme...@gmail.com To:Fossil Users Mailing List fossil-users@lists.fossil-scm.org Cc: Sent:Thursday, April 7, 2011 4:11 AM Subject:[fossil-users] CRLF conversion on windows Hi, Is there any plan for CRLF conversion under windows? This would be very usefull for cross platform projects. Especially when using Visual Studio on the Windows side, which silently add CRLF line ending on a LF only file which give you a mixed line ending file (got bunch of ^M when editing files with Vim after). it could convert text file from CR-LF to LF when committing and the oposite on checkout, so this would always keep LF line ending on repository and the local checkout on windows would have CR-LF line ending text file. Just like does Git and CVSNT (using Tortoise CVS at least). Of course this might be dangerous for data corruption when some binary file are flag as text file, but this kind of feature would be off by default for sure. -- Martin ___ 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 ___ 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 ___ 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] CRLF conversion on windows
Good to know! This came about from supporting data files supplied by various users and I still receive the occasional [CR] only data file? On Thu, Apr 7, 2011 at 12:33 PM, Konstantin Khomoutov flatw...@users.sourceforge.net wrote: On Thu, 7 Apr 2011 12:04:44 -0400 sky5w...@gmail.com wrote: I would be immensely confused if my SCM was modifying the contents of my source code and/or support documents. Given that MacOS has yet another EOL = [CR], it is better for your own code to manage distribution effects. I think it's no longer true: CR was used on prehistoric Macs (those from eighties); contemporary Macs are quite POSIX'y and have LF as a conventional line-ending marker. As to imaginable hassles of auto-conversions, I think this is an exaggregation: Subversion and Git do this for ages and there's no apparent complaints about how they do this. In case you're interested, here are explanations on how they do this: http://svnbook.red-bean.com/en/1.5/svn.advanced.props.file-portability.html#svn.advanced.props.special.eol-style http://www.kernel.org/pub/software/scm/git/docs/git-config.html (see core.eol, core.safecrlf, core.autocrlf; Git for Windows has core.autocrlf set to true by default). ___ 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] CRLF conversion on windows
There are countless operating systems available today, each with is own peccadillos. So why is it always windows that gives trouble? The more one tries to make code cross-platform, the more one realizes that windows is the problem child. The reality is that if you count any electronic device that can contain an OS, probably UNIX is included in more devices than Windows (or it will do in the future when even the house fridge will contain a processor running linux). But if you only count the devices that can potencially run fossil, 9 for every 10 of them are running Windows and are having the CR-LF problem as well as the code page problem. An you know, big brother always is right, isn't it? RR 2011/4/7 Richard Hipp d...@sqlite.org: On Thu, Apr 7, 2011 at 12:42 PM, Ramon Ribó ram...@compassis.com wrote: MacOSX is using UNIX line ending since more than 10 years-ago. In modern computers, there are two options: Unix/MacOSX: LF Also, Solaris, AIX, HPUX, NetBSD, OpenBSD, QNX, etc. Windows: CR-LF The odd man out. I would not see it as a problem that fossil changed line-endings if it was disabled by default and it could be enabled with something similar to: fossil setting ascii-glob *.c,*.h Another thing that would be a bonus for cross-platform development would be to change the encoding of the text files. In modern Linux it is utf-8. And in modern Windows, it is a code page that depends on the country but it is different from utf-8 Notice how everybody else uses utf8 for everything. Only on windows do we have issues with locale-dependent code pages. There are countless operating systems available today, each with is own peccadillos. So why is it always windows that gives trouble? The more one tries to make code cross-platform, the more one realizes that windows is the problem child. I understand that it is more reasonable to implement in a SCM only the line-ending change, but I wanted to write the encoding problem just for the record. Regards RR 2011/4/7 sky5w...@gmail.com: I would be immensely confused if my SCM was modifying the contents of my source code and/or support documents. Given that MacOS has yet another EOL = [CR], it is better for your own code to manage distribution effects. Just my opinion. -Steve On Thu, Apr 7, 2011 at 11:54 AM, Martin Gagnon eme...@gmail.com wrote: I know this new feature. But I'm really talking about converting the line ending, for cross platform development issue. -- Martin Le 2011-04-07 à 10:43, Clark Christensen cdcmi...@yahoo.com a écrit : I'm using fossil version [1d93222627] 2011-03-01 19:04:32 UTC With this version, Fossil warns about CRLF line ends on commit, and allows me to commit anyway, or abort and fix. This is a good option for me. Some files are OK with CRLFs and others are not. I like being able to choose. -Clark - Original Message - From:Martin Gagnon eme...@gmail.com To:Fossil Users Mailing List fossil-users@lists.fossil-scm.org Cc: Sent:Thursday, April 7, 2011 4:11 AM Subject:[fossil-users] CRLF conversion on windows Hi, Is there any plan for CRLF conversion under windows? This would be very usefull for cross platform projects. Especially when using Visual Studio on the Windows side, which silently add CRLF line ending on a LF only file which give you a mixed line ending file (got bunch of ^M when editing files with Vim after). it could convert text file from CR-LF to LF when committing and the oposite on checkout, so this would always keep LF line ending on repository and the local checkout on windows would have CR-LF line ending text file. Just like does Git and CVSNT (using Tortoise CVS at least). Of course this might be dangerous for data corruption when some binary file are flag as text file, but this kind of feature would be off by default for sure. -- Martin ___ 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 ___ 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 ___ 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 ___
Re: [fossil-users] CRLF conversion on windows
I never had problems with LF line endings in my batch files/source files/whatever I am on windows 7 with vs2010. The only thing whitch troubles me is the linux shell interpreter who can not live with CR-LF line endings and renames dirs to dir^M. For god sake let windows out of this, becouse it (currently) works better with different line endings than linux (currently) does. As you see. I'm sure it was different in the 80's and 90's. Back to the topic: Converting files between different OS is an unnecessary feature to me. You can convert more accurate if you write your own scripts to do that. That's like deleting unneeded files out of directories. I wrote a simple tcl script and qt programm to do that: http://sourceforge.net/projects/dircln/files/ 1. cleandir 2. dos2unix 3. fossil add * 4. fossil commit 5. dos2unix If someone does not want to use the 5 commands all the time, wrap it into a shell script. PS: Converting files to different line endings is already available on most systems. Even vs2010 can do it, and it's plugin and macro system is (almost) one of the best. Greetings, Louis Am 07.04.2011 18:55, schrieb Richard Hipp: On Thu, Apr 7, 2011 at 12:42 PM, Ramon Ribó ram...@compassis.com mailto:ram...@compassis.com wrote: MacOSX is using UNIX line ending since more than 10 years-ago. In modern computers, there are two options: Unix/MacOSX: LF Also, Solaris, AIX, HPUX, NetBSD, OpenBSD, QNX, etc. Windows: CR-LF The odd man out. I would not see it as a problem that fossil changed line-endings if it was disabled by default and it could be enabled with something similar to: fossil setting ascii-glob *.c,*.h Another thing that would be a bonus for cross-platform development would be to change the encoding of the text files. In modern Linux it is utf-8. And in modern Windows, it is a code page that depends on the country but it is different from utf-8 Notice how everybody else uses utf8 for everything. Only on windows do we have issues with locale-dependent code pages. There are countless operating systems available today, each with is own peccadillos. So why is it always windows that gives trouble? The more one tries to make code cross-platform, the more one realizes that windows is the problem child. I understand that it is more reasonable to implement in a SCM only the line-ending change, but I wanted to write the encoding problem just for the record. Regards RR 2011/4/7 sky5w...@gmail.com mailto:sky5w...@gmail.com: I would be immensely confused if my SCM was modifying the contents of my source code and/or support documents. Given that MacOS has yet another EOL = [CR], it is better for your own code to manage distribution effects. Just my opinion. -Steve On Thu, Apr 7, 2011 at 11:54 AM, Martin Gagnon eme...@gmail.com mailto:eme...@gmail.com wrote: I know this new feature. But I'm really talking about converting the line ending, for cross platform development issue. -- Martin Le 2011-04-07 à 10:43, Clark Christensen cdcmi...@yahoo.com mailto:cdcmi...@yahoo.com a écrit : I'm using fossil version [1d93222627] 2011-03-01 19:04:32 UTC With this version, Fossil warns about CRLF line ends on commit, and allows me to commit anyway, or abort and fix. This is a good option for me. Some files are OK with CRLFs and others are not. I like being able to choose. -Clark - Original Message - From:Martin Gagnon eme...@gmail.com mailto:eme...@gmail.com To:Fossil Users Mailing List fossil-users@lists.fossil-scm.org mailto:fossil-users@lists.fossil-scm.org Cc: Sent:Thursday, April 7, 2011 4:11 AM Subject:[fossil-users] CRLF conversion on windows Hi, Is there any plan for CRLF conversion under windows? This would be very usefull for cross platform projects. Especially when using Visual Studio on the Windows side, which silently add CRLF line ending on a LF only file which give you a mixed line ending file (got bunch of ^M when editing files with Vim after). it could convert text file from CR-LF to LF when committing and the oposite on checkout, so this would always keep LF line ending on repository and the local checkout on windows would have CR-LF line ending text file. Just like does Git and CVSNT (using Tortoise CVS at least). Of course this might be dangerous for data corruption when some binary file are flag as text file, but this kind of feature would be off by default for sure. -- Martin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org mailto:fossil-users@lists.fossil-scm.org
Re: [fossil-users] CRLF conversion on windows
Getting pedantic here... On Thu, 7 Apr 2011 12:55:14 -0400 Richard Hipp d...@sqlite.org wrote: On Thu, Apr 7, 2011 at 12:42 PM, Ramon Ribó ram...@compassis.com wrote: MacOSX is using UNIX line ending since more than 10 years-ago. In modern computers, there are two options: Unix/MacOSX: LF Also, Solaris, AIX, HPUX, NetBSD, OpenBSD, QNX, etc. Solaris, AIX and HPUX are UNIX(tm) systems, and are (or were, I haven't kept careful track) derived from ATT Unix distributions. NetBSD, OpenBSD and FreeBSD can all trace their genealogy back to ATT source code, but aren't UNIX(tm) systems, just Unix-like. For that matter, Mac OSX is a UNIX(tm) system, but shares the BSD genealogy instead of being derived from an ATT distribution. Also: Minix, Ubuntu, Redhat, Gentoo, Fedora, Debian, etc, which are Unix-like but have source code that never included ATT code. Windows: CR-LF There are countless operating systems available today, each with is own peccadillos. So why is it always windows that gives trouble? The more one tries to make code cross-platform, the more one realizes that windows is the problem child. Basically, Unix won. I think Windows is the last system maintaining backwards compatibility to systems that predate the rise of Unix. Pretty much everything else either was designed with the Unix model in mind, or converted to it somewhere along the way. At this point, I wouldn't be surprised if there were more Unix-like systems than Windows systems in the world, given that two of the three most popular smart phone/tablet OS's (IOS and Android) are Unix-like, and the popularity of Unix-like OS's on embedded devices. Most of them could probably be convinced to run a static build of fossil, but not a dynamic one, as there's a fair chance they've been stripped of one or more libraries that fossil needs. mike *) UNIX(tm) is a trademark of The Open Group, and can legally only be used to describe systems which The Open Group has certified as meeting the Single UNIX Specification. -- Mike Meyer m...@mired.org http://www.mired.org/consulting.html Independent Software developer/SCM consultant, email for more information. O ascii ribbon campaign - stop html mail - www.asciiribbon.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] tags branches after importing from CVS
* Joan Picanyol i Puig lists-fos...@biaix.org [20110407 17:28]: Various combinations of tag add tag cancel have ended up with (mispellings and all): jpicanyol@jpicanyol-desktop:~/wd$ fossil tag list --raw c57a6c30e7 branch=master branck branck=trunk sym-branck=trunk sym-sym-sym-trunk sym-sym-trunk sym-trunk trunk jpicanyol@jpicanyol-desktop:~/wd$ fossil tag list c57a6c30e7 I'm not quite sure on the meaning of all of these, and I'm not even sure how I'd want them to be. Some clues please? How is tag cancel supposed to work and how am I supposed verify it? http://fossil-scm.org/index.html/doc/trunk/www/fileformat.wiki#ctrl branch.c has the following comment: ** If tagtype is 2 then the tag is being propagated from an ** ancestor node. If tagtype is 0 it means a propagating tag is ** being blocked. Where are the magic tags modified by --raw defined? See above. Looking at the source it seems that --raw merely disables de automatic handling of the sym- prefix for the tagname. I'm confused on the existance of branch=branchname vs. sym-branchname. It appears redundant to me... Meanwhile, I've managed to kind-of-restore my repo after realising that fossil was happily treating tagname=tagvalue as a tag name. qvb -- pica ___ 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] crnl-setting bug
On Thu, Apr 7, 2011 at 1:16 PM, Scott Robison sc...@scottrobison.us wrote: I believe the glob-style wildcard pattern matching is being performed by mingw during program startup before handing control over to main (because cmd.exe does not do wildcard expansion itself in either Windows 7 or XP). Bah, stupid gmail (or stupid user of gmail). Anyway, if you type fossil setting crnl-glob * at a command prompt in an empty directory (no expansion opportunity for *) you get a different result than if you type that command in a non-empty directory (where * is expanded into the list of entries in the current directory). The mingw startup code is emulating the behavior one expects from a posix environment. SDR ___ 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] crnl-setting bug
On Thu, Apr 7, 2011 at 3:16 PM, Scott Robison sc...@scottrobison.us wrote: I believe the glob-style wildcard pattern matching is being performed by mingw during program startup before handing control over to main (because cmd.exe does not do wildcard expansion itself in either Windows 7 or XP). And, I would guess that cmd.exe is stripping off the s. So, maybe: fossil setting crnl-glob '*' would work. After cmd.exe strips off the s, 's would still be there to protect the * from mingw. ___ 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] crnl-setting bug
On Thu, Apr 7, 2011 at 1:24 PM, Ron Wilson ronw.m...@gmail.com wrote: On Thu, Apr 7, 2011 at 3:16 PM, Scott Robison sc...@scottrobison.us wrote: I believe the glob-style wildcard pattern matching is being performed by mingw during program startup before handing control over to main (because cmd.exe does not do wildcard expansion itself in either Windows 7 or XP). And, I would guess that cmd.exe is stripping off the s. So, maybe: fossil setting crnl-glob '*' would work. After cmd.exe strips off the s, 's would still be there to protect the * from mingw. Ah, excellent point. cmd.exe strips quotes so that there is a way to embed separator characters such as space in a command line argument. In any case, I just tested and it appears that using single quotes instead of double quotes is sufficient to get the asterisk through the command line processing software stack. SDR ___ 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] Embedding an attached image file?
Here's an example: http://tinyconcepts.com/fs.pl/hub.fsl/wiki?name=testJavaScript Click on your attachment and copy its URL from the resulting page: http://tinyconcepts.com/fs.pl/hub.fsl/attachview?page=testJavaScriptfile=tick.png Then, put it in an img tag in the wiki page: img src=... Bill On Mon, Apr 4, 2011 at 11:49 AM, Mike Meyer m...@mired.org wrote: I know I can embed an image file that's stored in the SCM. I'd like to embed - instead of just link to - an image file that's attached to a wiki page. Is that possible? If so, what's the syntax. The obvious things didn't work for me, and google just lists this as a TODO. thanks, mike -- Mike Meyer m...@mired.org http://www.mired.org/consulting.html Independent Software developer/SCM consultant, email for more information. O ascii ribbon campaign - stop html mail - www.asciiribbon.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
Are you on *NIX or Windows? If you're on *NIX, you can use fossil commit $(find dir -type f) or find dir -type f | xargs fossil commit Bill On Thu, Apr 7, 2011 at 5:14 AM, Anthony Jefferson ac_jeffer...@yahoo.comwrote: Typically when I do a commit I simply do : fossil commit From inside the tree of managed artifacts. However, yesterday I realized I was working on 2 different problems and wanted to commit only the single directory tree I was in. I looked up the syntax a realized I could give the commit command a list of files. Question: Is there a way to do a commit on an sub-hierarchy of files e.g. commit from a starting directory? I got the effect I wanted using individual files but it would have been easier to simply supply a directory name such as: fossil commit directory-x Thanks, Tony Jefferson ___ 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
On Thu, Apr 07, 2011 at 02:39:30PM -0500, Bill Burdick wrote: Are you on *NIX or Windows? If you're on *NIX, you can use fossil commit $(find dir -type f) or find dir -type f | xargs fossil commit I think it is not that easy! :) fossil commit only likes the files that have changed. On Thu, Apr 7, 2011 at 5:14 AM, Anthony Jefferson ac_jeffer...@yahoo.comwrote: Typically when I do a commit I simply do : fossil commit From inside the tree of managed artifacts. However, yesterday I realized I was working on 2 different problems and wanted to commit only the single directory tree I was in. I looked up the syntax a realized I could give the commit command a list of files. Question: Is there a way to do a commit on an sub-hierarchy of files e.g. commit from a starting directory? I got the effect I wanted using individual files but it would have been easier to simply supply a directory name such as: fossil commit directory-x Thanks, Tony Jefferson ___ 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 ___ 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] crnl-setting bug
Confirmed. Single quotes work on Win7. On Thu, Apr 7, 2011 at 3:33 PM, Scott Robison sc...@scottrobison.us wrote: On Thu, Apr 7, 2011 at 1:24 PM, Ron Wilson ronw.m...@gmail.com wrote: On Thu, Apr 7, 2011 at 3:16 PM, Scott Robison sc...@scottrobison.us wrote: I believe the glob-style wildcard pattern matching is being performed by mingw during program startup before handing control over to main (because cmd.exe does not do wildcard expansion itself in either Windows 7 or XP). And, I would guess that cmd.exe is stripping off the s. So, maybe: fossil setting crnl-glob '*' would work. After cmd.exe strips off the s, 's would still be there to protect the * from mingw. Ah, excellent point. cmd.exe strips quotes so that there is a way to embed separator characters such as space in a command line argument. In any case, I just tested and it appears that using single quotes instead of double quotes is sufficient to get the asterisk through the command line processing software stack. SDR ___ 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
Well then, nothing could be simpler than this! (of course you could put it
into a script -- this is for *NIX)
find $(fossil changes | awk '{print $2}') -wholename $dir/* | xargs fossil
commit
or, if you don't like find and awk, you can execute this from the top dir in
the project...
echo select pathname from vfile where chnged = 1 and pathname like
'$dir/%'; | fossil sqlite _FOSSIL_ | xargs fossil commit
Bill
2011/4/7 Lluís Batlle i Rossell virik...@gmail.com
On Thu, Apr 07, 2011 at 02:39:30PM -0500, Bill Burdick wrote:
Are you on *NIX or Windows? If you're on *NIX, you can use fossil commit
$(find dir -type f) or find dir -type f | xargs fossil commit
I think it is not that easy! :)
fossil commit only likes the files that have changed.
On Thu, Apr 7, 2011 at 5:14 AM, Anthony Jefferson
ac_jeffer...@yahoo.comwrote:
Typically when I do a commit I simply do :
fossil commit
From inside the tree of managed artifacts. However, yesterday I
realized I
was working on 2 different problems and wanted to commit only the
single
directory tree I was in. I looked up the syntax a realized I could give
the
commit command a list of files.
Question:
Is there a way to do a commit on an sub-hierarchy of files e.g. commit
from
a starting directory?
I got the effect I wanted using individual files but it would have been
easier to simply supply a directory name such as:
fossil commit directory-x
Thanks,
Tony Jefferson
___
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
___
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] crnl-setting bug
Confirmed. Single quotes work on Win7. Actually, single quotes don't work either because the single quotes get preserved in fossil: PS C:\rev\src\fossil cmd Microsoft Windows [Version 6.0.6002] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\rev\src\fossilfossil setting crnl-glob '*' C:\rev\src\fossilfossil settings access-log auto-captcha auto-shun autosync (local) 1 binary-glob clearsign crnl-glob(local) '*' default-perms diff-command dont-push editor gdiff-command gmerge-command https-login ignore-glob http-port localauth(local) 0 main-branch manifest (local) 1 max-upload mtime-changes pgp-command proxy repo-cksum self-register ssh-command web-browser Ron Wilson, Engineering Project Lead (o) 434.455.6453, (m) 434.851.1612, www.harris.com HARRIS CORPORATION | RF Communications Division assuredcommunications(tm) ___ 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] crnl-setting bug
On Thu, Apr 7, 2011 at 2:44 PM, Wilson, Ronald rwils...@harris.com wrote: Confirmed. Single quotes work on Win7. Actually, single quotes don't work either because the single quotes get preserved in fossil: According to http://gnuwin32.sourceforge.net/compile.html: Filename globbing Wildcards on the command-line are expanded by the command-line interpreter. If you wish to disable this filename globbing, then add int _CRT_glob = 0; to the beginning of the main program file. Perhaps this will be necessary for Windows builds. SDR ___ 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] CRLF conversion on windows
Basically, Unix won. I think Windows is the last system maintaining backwards compatibility to systems that predate the rise of Unix. Pretty much everything else either was designed with the Unix model in mind, or converted to it somewhere along the way. How is abandoning backwards compatibility in any way linked to winning? Frankly, I’m surprised at how often MS seems to get beat up on this list; many of us are Windows users and developers. Personally it gets under my skin; maybe it shouldn't. Kudos to Windows for supporting customers with backwards compatibility and interoperability - something that other operating systems apparently can't be burdened with. RW Ron Wilson, Engineering Project Lead (o) 434.455.6453, (m) 434.851.1612, www.harris.com HARRIS CORPORATION | RF Communications Division assuredcommunications™ ___ 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] crnl-setting bug
I wonder if this would affect commands like fossil add *.txt Bill On Thu, Apr 7, 2011 at 3:50 PM, Scott Robison sc...@scottrobison.us wrote: On Thu, Apr 7, 2011 at 2:44 PM, Wilson, Ronald rwils...@harris.com wrote: Confirmed. Single quotes work on Win7. Actually, single quotes don't work either because the single quotes get preserved in fossil: According to http://gnuwin32.sourceforge.net/compile.html: Filename globbing Wildcards on the command-line are expanded by the command-line interpreter. If you wish to disable this filename globbing, then add int _CRT_glob = 0; to the beginning of the main program file. Perhaps this will be necessary for Windows builds. SDR ___ 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] crnl-setting bug
LOL...I didn't check the resultant settings. Bummer, so we gotta use the ui for windows 7 and beyond? On Thu, Apr 7, 2011 at 4:44 PM, Wilson, Ronald rwils...@harris.com wrote: Confirmed. Single quotes work on Win7. Actually, single quotes don't work either because the single quotes get preserved in fossil: PS C:\rev\src\fossil cmd Microsoft Windows [Version 6.0.6002] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\rev\src\fossilfossil setting crnl-glob '*' C:\rev\src\fossilfossil settings access-log auto-captcha auto-shun autosync (local) 1 binary-glob clearsign crnl-glob (local) '*' default-perms diff-command dont-push editor gdiff-command gmerge-command https-login ignore-glob http-port localauth (local) 0 main-branch manifest (local) 1 max-upload mtime-changes pgp-command proxy repo-cksum self-register ssh-command web-browser Ron Wilson, Engineering Project Lead (o) 434.455.6453, (m) 434.851.1612, www.harris.com HARRIS CORPORATION | RF Communications Division assuredcommunications(tm) ___ 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
I did some back searching and found out that this feature does not exist in
fossil. I will probably use a script to get the results I want. Thanks for the
find/awk idea. I'm doing most of my work on windows but have the Cygwin stuff
installed so something close to that should work.
Thanks all for the responses.
Tony
--- On Thu, 4/7/11, Bill Burdick bill.burd...@gmail.com wrote:
From: Bill Burdick bill.burd...@gmail.com
Subject: Re: [fossil-users] Commit Question
To: fossil-users@lists.fossil-scm.org
Date: Thursday, April 7, 2011, 4:38 PM
Well then, nothing could be simpler than this! (of course you could put it
into a script -- this is for *NIX)
find $(fossil changes | awk '{print $2}') -wholename $dir/* | xargs fossil
commit
or, if you don't like find and awk, you can execute this from the top dir in
the project...
echo select pathname from vfile where chnged = 1 and pathname like '$dir/%';
| fossil sqlite _FOSSIL_ | xargs fossil commit
Bill
2011/4/7 Lluís Batlle i Rossell virik...@gmail.com
On Thu, Apr 07, 2011 at 02:39:30PM -0500, Bill Burdick wrote:
Are you on *NIX or Windows? If you're on *NIX, you can use fossil commit
$(find dir -type f) or find dir -type f | xargs fossil commit
I think it is not that easy! :)
fossil commit only likes the files that have changed.
On Thu, Apr 7, 2011 at 5:14 AM, Anthony Jefferson
ac_jeffer...@yahoo.comwrote:
Typically when I do a commit I simply do :
fossil commit
From inside the tree of managed artifacts. However, yesterday I realized I
was working on 2 different problems and wanted to commit only the single
directory tree I was in. I looked up the syntax a realized I could give the
commit command a list of files.
Question:
Is there a way to do a commit on an sub-hierarchy of files e.g. commit from
a starting directory?
I got the effect I wanted using individual files but it would have been
easier to simply supply a directory name such as:
fossil commit directory-x
Thanks,
Tony Jefferson
___
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
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
-Inline Attachment Follows-
___
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] CRLF conversion on windows
On Thu, Apr 7, 2011 at 4:56 PM, Wilson, Ronald rwils...@harris.com wrote: How is abandoning backwards compatibility in any way linked to winning? Frankly, I’m surprised at how often MS seems to get beat up on this list; many of us are Windows users and developers. Personally it gets under my skin; maybe it shouldn't. Kudos to Windows for supporting customers with backwards compatibility and interoperability - something that other operating systems apparently can't be burdened with. Unix/Linux per se, dosen't care about line endings. At least some versions of the more/less/page utility do auto-detect line endings and do the right thing. The various command line shells are less good at this - but those are not actually tired to Unix/Linux, and if you build them for Windows with out proper configuration, they will have as much trouble with line endings on Windows as they do on Unix/Linux when fed a file with line endings other than just plain LFs. True, Windows does (or did) have a text mode when opening files, but even this is under control of the application requesting a file be opened. For the most part, applications that parse or manipulate the text inside files should be responsible for coping with various line ending conventions, not the OS, or other tools that treat files as opaque containers. VCS apps are in a gray area. Their primary mission is to manage revisions of files. However, various concerns, especially effificency, make it desiable to get inside those files for the purpose of finding the smallest set of differences between revisions so as to store just the differences against a reference copy, rather than stroing a full copy of each revision. While not essential, being able to cope with differences in line endings can make the difference sets smaller. Code Page / Character Set incompatabilities are a much bigger issue. Because auto-detection of the code page is impractical in most cases, it is better to configure the needed translations rather than rely on the tools to guess correctly. As such, probably better to handle with the hook mechanism when it becomes available. ___ 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] crnl-setting bug
On Thu, Apr 07, 2011 at 05:15:12PM -0400, sky5w...@gmail.com wrote: Confirmed. Single quotes work on Win7. Actually, single quotes don't work either because the single quotes get preserved in fossil: PS C:\rev\src\fossil cmd Microsoft Windows [Version 6.0.6002] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\rev\src\fossilfossil setting crnl-glob '*' C:\rev\src\fossilfossil settings access-log auto-captcha auto-shun autosync (local) 1 binary-glob clearsign crnl-glob (local) '*' [...] LOL...I didn't check the resultant settings. Bummer, so we gotta use the ui for windows 7 and beyond? Could you please try fossil settings crnl-glob \* under Windows 7? The backslash has no special meaning to cmd.exe, so may be MinGW detects such escaping? In either case, it's not clear why its globbing behaviour differs between versions of the OS. This looks like a bug in MinGW runtime. ___ 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] crnl-setting bug
you at correct. we need file expansion on globs, just not in this case. I'll be content to use the ui for this one. rw from my mobile 434.851.1612 On Apr 7, 2011, at 4:59 PM, Bill Burdick bill.burd...@gmail.commailto:bill.burd...@gmail.com wrote: I wonder if this would affect commands like fossil add *.txt Bill On Thu, Apr 7, 2011 at 3:50 PM, Scott Robison mailto:sc...@scottrobison.ussc...@scottrobison.usmailto:sc...@scottrobison.us wrote: On Thu, Apr 7, 2011 at 2:44 PM, Wilson, Ronald mailto:rwils...@harris.comrwils...@harris.commailto:rwils...@harris.com wrote: Confirmed. Single quotes work on Win7. Actually, single quotes don't work either because the single quotes get preserved in fossil: According to http://gnuwin32.sourceforge.net/compile.html http://gnuwin32.sourceforge.net/compile.html: Filename globbing Wildcards on the command-line are expanded by the command-line interpreter. If you wish to disable this filename globbing, then add int _CRT_glob = 0; to the beginning of the main program file. Perhaps this will be necessary for Windows builds. SDR ___ fossil-users mailing list mailto:fossil-users@lists.fossil-scm.orgfossil-users@lists.fossil-scm.orgmailto:fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-usershttp://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ 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 ___ 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] tags branches after importing from CVS
Joan Picanyol i Puig schrieb: (...) Hello Joan, first you have to understand, that tags in Fossil are what other VCSs call properties. That means, there is the possibility to assign a value to a property/tag if one wants to. Then those properties/tags can be chosen to propagate automatically down the descendants chain of child revisions, or they are only valid for a certain commit only. How is tag cancel supposed to work and how am I supposed verify it? If you chose to cance a tag/property it means, that the tag will not be regarded as associated with that commit anymore. It is still sitting on this commit, but will not apply on it. If the tag had a value, that value is lost afterwards. Furthermore the tag will not any longer propagate to the descendants if it was a propagating tag. Therefore it is also cancelled for the descendants. You can verify this via the 'fossil ui' command, that show you those tags striked out. (...) ** If tagtype is 2 then the tag is being propagated from an ** ancestor node. If tagtype is 0 it means a propagating tag is ** being blocked. Where are the magic tags modified by --raw defined? See above. Looking at the source it seems that --raw merely disables de automatic handling of the sym- prefix for the tagname. Yes! If you create a tag via option --propagate the tag type is propagating. If you issue a fossil tag cancel ... the tag type will be propagation blocked (or tag cancelled) AFAIR ... I'm confused on the existance of branch=branchname vs. sym-branchname. It appears redundant to me... All tags that begin with prefix sym- can be used at command line instead of the SHA1 sum of a commit. So at your example above I could use fossil co branchname because the tag was called sym-branchname. The last commit with that tag applied will be checked out then. The property branch does not contain any sym- prefix and therefore *cannot* being used at command line to select a commit instead of using its SHA1 sum. But as it has assigned a value to it (branch=branchname) Fossil know on which branch the current commit currently resides. If there were no such property, Fossil wouldn't know the current branch, as there could be more than one tag with a sym- prefix prepended -- propagating or not (e.g. release, fix, testing, ...) Best regards and happy Fossiling, chi :-) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] A crazy idea, but perhaps it has merit ...
I don't have a lot of public stuff out there yet (my fossils are at www.kiatoa.com/fossils/opensrc) but there have been several times where I made a typo or minor mistake and it would have saved some embarrassment *and* been really cool to be able to browse to the file and make a change and check it in from the web interface (from my phone for example). Between the /doc feature and the wiki it doesn't seem like much of a leap to being able to modify files on a branch. In fact being able to edit the files in /doc almost makes the need for the independently maintained wiki redundant. Conceptually I think it is natural for the wiki to be another directory in most projects. Although I suppose it may not work to force everyone to keep the wiki as part of the controlled code. Has this been discussed before? If so can someone send me a pointer to the thread? A quick search didn't yield anything. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
