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
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
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,
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
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
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
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
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
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,
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
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
Command: Fossil commit -m Added Test.bat Test.bat
Response: Test.bat contains CR/NL line endings; commit anyhow (y/N/a)?
Of course it does. All Windows text files contain /r/n.
Why is Fossil asking this question and, more importantly, how do I make it stop?
This must have been added within the
On Mon, Apr 4, 2011 at 11:46 AM, Tony Perovic tpero...@compumation.comwrote:
Command: Fossil commit -m Added Test.bat Test.bat
Response: Test.bat contains CR/NL line endings; commit anyhow (y/N/a)?
Of course it does. All Windows text files contain /r/n.
Why is Fossil asking this
On Mon, 4 Apr 2011 10:46:03 -0500
Tony Perovic tpero...@compumation.com wrote:
Command: Fossil commit -m Added Test.bat Test.bat
Response: Test.bat contains CR/NL line endings; commit anyhow (y/N/a)?
Of course it does. All Windows text files contain /r/n.
Why is Fossil asking this
-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
:
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
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
17 matches
Mail list logo