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] 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] 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] Commit question
On Apr 4, 2011, at 22:55 , Stephan Beal wrote: On a related note: some tools (like cvs or svn) warn if a file's last line has no end-of-line marker. That's because (as i was taught, anyway) the official definition of a text file is basically variable-length records separated by a record separator (an end-of-line sequence (\n on *nix, \r\n on Windows)), and that the last record must also have such a separator. Actually, this way the definition says that the last line can not have a \n. You probably wanted to write ended by a record separator, but then the word separator is misleading ;) Kind regards, Remigiusz Modrzejewski ___ 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 Tue, Apr 5, 2011 at 3:49 PM, Remigiusz Modrzejewski l...@maxnet.org.pl wrote: On Apr 4, 2011, at 22:55 , Stephan Beal wrote: On a related note: some tools (like cvs or svn) warn if a file's last line has no end-of-line marker. That's because (as i was taught, anyway) the official definition of a text file is basically variable-length records separated by a record separator (an end-of-line sequence (\n on *nix, \r\n on Windows)), and that the last record must also have such a separator. Actually, this way the definition says that the last line can not have a \n. You probably wanted to write ended by a record separator, but then the word separator is misleading ;) I recall it being defined as variable length records, each ending with a record terminator, which was, because of the way teletype machine worked, CR-LF. (Though, with the real machine, LF-CR had the same end result.) Interestingly, Microsoft choose control-Z as end-of-file, rather than any of the other defined control values that might have been better. My guess is that that was because Z is the last letter of the alphabet, and Z being closest to the lower left corner of the keyboard. ___ 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
Sometime on 4/5/2011, Ron Wilson wrote: Interestingly, Microsoft choose control-Z as end-of-file, rather than any of the other defined control values that might have been better. My guess is that that was because Z is the last letter of the alphabet, and Z being closest to the lower left corner of the keyboard. For some reason, that sets off an urge to reminisce about old computers... Ctrl+Z was used as an end of file mark in CP/M-80, and DOS 1.0 had a lot of CP/M heritage and inspiration. That is where drive letters and 8.3 file names come from, for instance. Ctrl+Z (or some marker, at least) was needed because the CP/M file system stored files in whole disk blocks, and had no other way of marking the end of a file to single-byte accuracy. CP/M wasn't alone in this choice. Digital's RT-11 also stored files in whole block increments and used Ctrl+Z as EOF. IIRC, very early versions of DOS followed the same conventions, and many old utilities would pad files out to block boundaries or at least insert a Ctrl+Z after the last byte written. To this day, files opened in Text on Windows will report EOF at the first Ctrl+Z encountered, although all versions of the FAT file system and its descendents know the file size in bytes. As a further bit of trivia, PNG files include a Ctrl+Z in their header to explicitly catch the case that the file was opened with text-mode translations enabled. In that case, the file will appear to end after six bytes are read. The header is: 0x89 0x50 0x4E 0x47 0x0d 0x0a 0x1a 0x0a. This sequence catches a bunch of incorrect ways to process the file including 7-bit only transmission, CRLF to NL, NL to CRLF, Ctrl+Z as EOF, and byte order. And if you use TYPE at the command prompt to display a PNG file, it will show the string PNG before stopping. Incidentally, the use of Ctrl+D in Unix derivatives is a property of the tty driver and it does not get translated as EOF when read from files at all. Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.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] Commit question
I believe Ctrl-Z is defined as EOF in ASCII which predates Microsoft. Terminating text files with EOF was the solution employeed by CP/M because file sizes were a sector count instead of a byte count. On Apr 5, 2011 3:06 PM, Ron Wilson ronw.m...@gmail.com wrote: On Tue, Apr 5, 2011 at 3:49 PM, Remigiusz Modrzejewski l...@maxnet.org.pl wrote: On Apr 4, 2011, at 22:55 , Stephan Beal wrote: On a related note: some tools (like cvs or svn) warn if a file's last line has no end-of-line marker. That's because (as i was taught, anyway) the official definition of a text file is basically variable-length records separated by a record separator (an end-of-line sequence (\n on *nix, \r\n on Windows)), and that the last record must also have such a separator. Actually, this way the definition says that the last line can not have a \n. You probably wanted to write ended by a record separator, but then the word separator is misleading ;) I recall it being defined as variable length records, each ending with a record terminator, which was, because of the way teletype machine worked, CR-LF. (Though, with the real machine, LF-CR had the same end result.) Interestingly, Microsoft choose control-Z as end-of-file, rather than any of the other defined control values that might have been better. My guess is that that was because Z is the last letter of the alphabet, and Z being closest to the lower left corner of the keyboard. ___ 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
At 06:37 PM 4/5/2011, Scott Robinson wrote: I believe Ctrl-Z is defined as EOF in ASCII... In ASCII, Ctrl+Z is SUB, intended to substitute for a damaged character read from tape or received in a channel. ASCII did not define a specific end of file code. The closest are Ctrl+C aka ETX for End of Transmission, and Ctrl+D aka EOT for End of Text. Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.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] Commit question
Ah, thank you. I am on the road with barely enough bandwidth to email. At least I was smart enough to give myself an out with I believe instead of stating it as solid fact. :) SDR On Apr 5, 2011 6:48 PM, Ross Berteig r...@cheshireeng.com wrote: At 06:37 PM 4/5/2011, Scott Robinson wrote: I believe Ctrl-Z is defined as EOF in ASCII... In ASCII, Ctrl+Z is SUB, intended to substitute for a damaged character read from tape or received in a channel. ASCII did not define a specific end of file code. The closest are Ctrl+C aka ETX for End of Transmission, and Ctrl+D aka EOT for End of Text. Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ ___ 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 Mon, Apr 4, 2011 at 11:46 AM, Tony Perovic tpero...@compumation.comwrote: Command: Fossil commit -m Added Test.bat Test.bat Response: Test.bat contains CR/NL line endings; commit anyhow (y/N/a)? Of course it does. All Windows text files contain /r/n. Why is Fossil asking this question and, more importantly, how do I make it stop? fossil setting crnl-glob * This must have been added within the last few weeks because I never saw it until I upgraded to the latest version of Fossil. Added on 2011-02-25 *TONY PEROVIC* tpero...@compumation.com www.compumation.com 205 W. Grand Ave., Ste. 121 Bensenville, IL 60106 630-860-1921 Phone 630-860-1928 Fax ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org image002.jpg___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Commit question
On Mon, 4 Apr 2011 10:46:03 -0500 Tony Perovic tpero...@compumation.com wrote: Command: Fossil commit -m Added Test.bat Test.bat Response: Test.bat contains CR/NL line endings; commit anyhow (y/N/a)? Of course it does. All Windows text files contain /r/n. Why is Fossil asking this question and, more importantly, how do I make it stop? http://www.fossil-scm.org/fossil/info/046658848c21cd54749a48bebe7719d62cc9ecef You will discover another side of this problem when you attempt to do something like C:\ fossil diff | gvim -R - ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Commit question
Just curious: why is cr/lf in text files undesirable? Tony Perovic Compumation, Inc. From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Richard Hipp Sent: Monday, April 04, 2011 10:51 AM To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] Commit question On Mon, Apr 4, 2011 at 11:46 AM, Tony Perovic tpero...@compumation.commailto:tpero...@compumation.com wrote: Command: Fossil commit -m Added Test.bat Test.bat Response: Test.bat contains CR/NL line endings; commit anyhow (y/N/a)? Of course it does. All Windows text files contain /r/n. Why is Fossil asking this question and, more importantly, how do I make it stop? fossil setting crnl-glob * This must have been added within the last few weeks because I never saw it until I upgraded to the latest version of Fossil. Added on 2011-02-25 [cid:image001.jpg@01CBF2BB.0AFB0420] TONY PEROVIC tpero...@compumation.commailto:tpero...@compumation.com www.compumation.comhttp://www.compumation.com 205 W. Grand Ave., Ste. 121 Bensenville, IL 60106 630-860-1921tel:630-860-1921 Phone 630-860-1928tel:630-860-1928 Fax ___ fossil-users mailing list fossil-users@lists.fossil-scm.orgmailto:fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.orgmailto:d...@sqlite.org inline: image001.jpg___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Commit question
Thanks! That was a pain. On Mon, Apr 4, 2011 at 12:25 PM, Tony Perovic tpero...@compumation.comwrote: Just curious: why is cr/lf in text files undesirable? Tony Perovic Compumation, Inc. -- *From:* fossil-users-boun...@lists.fossil-scm.org [mailto: fossil-users-boun...@lists.fossil-scm.org] *On Behalf Of *Richard Hipp *Sent:* Monday, April 04, 2011 10:51 AM *To:* fossil-users@lists.fossil-scm.org *Subject:* Re: [fossil-users] Commit question On Mon, Apr 4, 2011 at 11:46 AM, Tony Perovic tpero...@compumation.com wrote: Command: Fossil commit -m Added Test.bat Test.bat Response: Test.bat contains CR/NL line endings; commit anyhow (y/N/a)? Of course it does. All Windows text files contain /r/n. Why is Fossil asking this question and, more importantly, how do I make it stop? fossil setting crnl-glob * This must have been added within the last few weeks because I never saw it until I upgraded to the latest version of Fossil. Added on 2011-02-25 *TONY PEROVIC* tpero...@compumation.com www.compumation.com 205 W. Grand Ave., Ste. 121 Bensenville, IL 60106 630-860-1921 Phone 630-860-1928 Fax ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Commit question
On Mon, Apr 4, 2011 at 6:25 PM, Tony Perovic tpero...@compumation.comwrote: Just curious: why is cr/lf in text files undesirable? On *nix systems, the line ending is \n, and having extra newlines in files can actually break them. i've seen, several times, cases where Windows-based Java developers edit a shell script, check it in, release the software, and then the scripts won't run on the customer's target (Unix) system because the shell name /bin/sh\r is not recognized as a shell/command. Some Windows editors can handle and/or emit Unix-style line-ends, but notepad does not. On a related note: some tools (like cvs or svn) warn if a file's last line has no end-of-line marker. That's because (as i was taught, anyway) the official definition of a text file is basically variable-length records separated by a record separator (an end-of-line sequence (\n on *nix, \r\n on Windows)), and that the last record must also have such a separator. -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
