On Sun, Dec 22, 2013 at 9:57 PM, wrote:
> Really, I am only implying some minimal file statistic like 'DeltaSize(%)'
> or somesuch to show the user it is in fact compared internally. The current
> message contradicts what is in fact happening. Maybe change that message to
> "Cannot visually displ
Really, I am only implying some minimal file statistic like 'DeltaSize(%)'
or somesuch to show the user it is in fact compared internally. The current
message contradicts what is in fact happening. Maybe change that message to
"Cannot visually display binary diffs. DeltaSize(%) = -10".
On Sun, De
On Sun, Dec 22, 2013 at 9:06 PM, wrote:
> Thanks. I didn't know how binary was handled given the Timeline diff
> response = "cannot compute difference between binary files".
>
That message is a bit misleading. It really means a "visual difference."
There isn't a mechanism to show a textual diff
Thanks. I didn't know how binary was handled given the Timeline diff
response = "cannot compute difference between binary files".
I think it would be cool if instead fossil listed some of the metrics used
or determined in the binary delta operation.
Thanks for Fossil!
On Sun, Dec 22, 2013 at 2:5
On Sun, Dec 22, 2013 at 8:44 PM, wrote:
> Ah, is there a way to quantify the binary delta?
> If I have a 1MB binary file and commit a 1 byte change, what is the size
> of the computed binary delta?
>
Very, very small:
Create two binaries with a one-byte difference:
[stephan@host:~/cvs/fossil/l
Ah, is there a way to quantify the binary delta?
If I have a 1MB binary file and commit a 1 byte change, what is the size of
the computed binary delta?
You are correct of course, but I tend not to extend the spirit of fossil to
binary files and images. It is their existence and not legacy that is
On Sun, Dec 22, 2013 at 7:37 PM, wrote:
> I am curious what is stored in the repo for each new commit that includes
> a tiny change to a binary file.
> Whether a dll or an image file, is fossil storing each binary file
> compressed, uncompressed or some sort of delta?
> Over time(6mo's to 1yr), I
On Sun, Dec 22, 2013 at 1:37 PM, wrote:
> I am curious what is stored in the repo for each new commit that includes
> a tiny change to a binary file.
> Whether a dll or an image file, is fossil storing each binary file
> compressed, uncompressed or some sort of delta?
>
A binary delta.
> Ove
I am curious what is stored in the repo for each new commit that includes a
tiny change to a binary file.
Whether a dll or an image file, is fossil storing each binary file
compressed, uncompressed or some sort of delta?
Over time(6mo's to 1yr), I would like to reduce my repo size by purging
really
9 matches
Mail list logo
