On 7/27/15, Andy Bradford wrote:
> Thus said Stephan Beal on Mon, 27 Jul 2015 14:28:11 +0200:
>
>> Somewhere the compressed size must be available because the repo stats
>> page/command (dbstat) shows the compression space savings. i'm still
>> at work and can't look into it now, but check the
Thus said Stephan Beal on Mon, 27 Jul 2015 14:28:11 +0200:
> Somewhere the compressed size must be available because the repo stats
> page/command (dbstat) shows the compression space savings. i'm still
> at work and can't look into it now, but check the code for the dbstat
> command.
I haven'
On Mon, Jul 27, 2015 at 2:25 PM, Michai Ramakers
wrote:
> Alright, thank you. Fwiw, the size I was interested in is what's
> stored in .git/* - I'm effectively storing Git checkouts in Fossil for
> this project... So I was interested in the overhead of that.
>
Somewhere the compressed size must
On 27 July 2015 at 14:21, Stephan Beal wrote:
> On Sun, Jul 26, 2015 at 9:47 PM, Michai Ramakers
> wrote:
>>
>> is the total number of bytes in a commit (the cumulative size of the
>> diffs) of a check-in visible somewhere?
>
> to get that you'll need to sum() the blob.size value of all files in
On Sun, Jul 26, 2015 at 9:47 PM, Michai Ramakers
wrote:
> Hello,
>
> is the total number of bytes in a commit (the cumulative size of the
> diffs) of a check-in visible somewhere?
to get that you'll need to sum() the blob.size value of all files in the
commit (the .size refers to its uncompress
Hello,
is the total number of bytes in a commit (the cumulative size of the
diffs) of a check-in visible somewhere?
thx,
Michai
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fos
6 matches
Mail list logo
