On Sun, Dec 7, 2014 at 8:02 PM, to...@acm.org wrote:
I could claim that a file containing all 256 ASCII codes is a text file
for my use. On the contrary I could also
That's the thing: there AREN'T 256 ASCII points. ASCII defines only 7, with
the 8th being being used by applications back in
On Mon, Dec 8, 2014 at 7:44 PM, Robert Engelhardt m...@robert-engelhardt.de
wrote:
Was anyone able to reproduce my problem or to understand what's going on
here? I have the impression that some parts of fossil are (correctly) not
case sensitive while others are, and in the case demonstrated
On 12/5/2014 6:38 PM, John P. Rouillard wrote:
I guess the same question is once I have tickets in fossil, is there
an export mechanism of some sort in case I want to move to another
system?
If you build fossil with JSON support (./configure --json) then you can
use a ticket report to export
On Mon, Dec 8, 2014 at 9:04 PM, Ross Berteig r...@cheshireeng.com wrote:
and find the JSON results on stdout.
[1]: https://docs.google.com/document/d/1fXViveNhDbiXgCuE7QDXQOKeFzf2q
NUkBEgiUvoqFN4/view
And in related news, the JSON API hits a milestone: AFAIK, that's the first
time someone
Stephan,
If it has ANY bytes above 127, it's not, by definition, ASCII. i.e.
it's binary.
I would disagree with part of this statement. I agree that ASCII defines
only the 7-bit code values, but I think this whole thread has run off
the rails in talking about the content values as
On Mon, Dec 08, 2014 at 12:09:57PM -0800, Shal Farley wrote:
Stephan,
If it has ANY bytes above 127, it's not, by definition, ASCII. i.e.
it's binary.
I would disagree with part of this statement. I agree that ASCII
defines only the 7-bit code values, but I think this whole thread
has
Does the mode (text/binary) factor into the sha1 fingerprint hash of
an artifact (single file) or commit ?
-bch
On 12/8/14, Martin Gagnon eme...@gmail.com wrote:
On Mon, Dec 08, 2014 at 12:09:57PM -0800, Shal Farley wrote:
Stephan,
If it has ANY bytes above 127, it's not, by definition,
On Mon, Dec 8, 2014 at 3:22 PM, bch brad.har...@gmail.com wrote:
Does the mode (text/binary) factor into the sha1 fingerprint hash of
an artifact (single file) or commit ?
No. The mode is only used to determine how to display the content on a
webpage. Also, independent changes can only be
On Mon, Dec 8, 2014 at 9:09 PM, Shal Farley s...@cheshireeng.com wrote:
I would disagree with part of this statement. I agree that ASCII defines
only the 7-bit code values, but I think this whole thread has run off the
rails in talking about the content values as determining whether the file
On Mon, Dec 08, 2014 at 03:28:30PM -0500, Richard Hipp wrote:
On Mon, Dec 8, 2014 at 3:22 PM, bch brad.har...@gmail.com wrote:
Does the mode (text/binary) factor into the sha1 fingerprint hash of
an artifact (single file) or commit ?
No. The mode is only used to
How about this idea?
During 'commit' when asked
file contains binary data. Use --no-warnings or the binary-glob setting
to disable this warning.
Commit anyhow (a=all/y/N)?
to have one more option (Text) to override the automatic detection.
Something like:
file contains binary data. Use
On 12/8/2014 12:07 PM, Stephan Beal wrote:
And in related news, the JSON API hits a milestone: AFAIK, that's the
first time someone other than myself has posted that link ;).
Stephen, it is a great example of API documentation. We should all
aspire to document our code as well. My only real
Thus said Richard Hipp on Mon, 08 Dec 2014 15:28:30 -0500:
So what is the point of this? Why is the default text/binary detection
not working for Tony?
I looked at the two files he sent as an example, and they had a null
byte (0x00) at the end of the file.
Andy
--
TAI64 timestamp:
On 12/7/2014 10:35 AM, Andy Bradford wrote:
I downloaded your zip file and looked at the
files and discovered that the last few bytes of each file has some
control characters (0x1a, 0x1d), null characters (0x00) and one has an
extended ASCII character 0xe6.
$ od -x 9s08gw32.s8p |
Thus said Richard Hipp on Mon, 08 Dec 2014 15:28:30 -0500:
So what is the point of this? Why is the default text/binary detection
not working for Tony?
And more specifically (I didn't know about this command until Stephen
showed it):
$ fossil test-looks-like-utf 9s08gw32.s8p
File
On Sun, Dec 7, 2014 at 12:35 PM, Stephan Beal sgb...@googlemail.com wrote:
On Sun, Dec 7, 2014 at 6:55 PM, to...@acm.org wrote:
The problem: A (mostly) text file with just a few normally non-text chars
which confuse fossil into thinking the whole file is binary.
There's an irony in there
16 matches
Mail list logo
