Re: [fossil-users] src/blob.c : blob_read_from_file overflow int size

On Tue, Jun 13, 2017 at 9:10 AM, wrote: > Nobody will put big files, but there are logic defects > > int size; > > file size is INT_MAX + 1 then size is negative(INT_MIN) > Actually, that's not guaranteed. The C standard guarantees overflow/underflow behaviour only

[fossil-users] blob.c : blob_trim , cast unsigned int into int, and re-cast

blob.c : blob_trim   line 538   https://www.fossil-scm.org/index.html/artifact?ln=538=febcddb2025c8da7 p->nUsed is unsigned int but while loop is int    538    int n = p->nUsed;    539    while( n>0 && fossil_isspace(z[n-1]) ){ n--; }    540    p->nUsed =

[fossil-users] Feature request : mimetype suffixes pas, pp, php, vbs, cpp, 7z

Feature request src/doc.c : https://www.fossil-scm.org/index.html/artifact?ln=75=e21c027580de8bf3 aMime[] mimetypes based on file suffixes Delphi source file { "pas",    3, "text/plain"    }, Free pascal source file { "pp", 2, "text/plain"   

Re: [fossil-users] Bug: Unable to clone

Richard, That seems to have fixed it: $ cd ~/devel/aurae $ /home/rkeene/devel/fossil/fossil version This is fossil version 2.3 [3200a7c72e] 2017-06-13 05:12:55 UTC $ /home/rkeene/devel/fossil/fossil rebuild 100.0% complete... rebuilding

Re: [fossil-users] src/blob.c : blob_read_from_file overflow int size

On Tue, Jun 13, 2017 at 04:19:53PM +0900, kowlsd3pw...@yahoo.co.jp wrote: > > [837333fc] Fix the blob_read_from_file > thank you. Actually, it is not completely fix because blob_read_from_file() call blob_read_from_channel() which return a int. Anyway, since the internals of the Blob

Re: [fossil-users] src/blob.c : blob_read_from_file overflow int size

On Tue, Jun 13, 2017 at 3:03 PM, Martin Gagnon wrote: > However, I think the best types for Blob structure is probably size_t. > I'm not sure if it's okay to use size_t with C89, but fossil already use > it in some places (even in blob.c), so I guess it's not a problem. >

Re: [fossil-users] What is the best way to update to a new upstream version

On 6/13/2017 12:52 PM, Joerg Sonnenberger wrote: On Tue, Jun 13, 2017 at 12:17:46PM -0500, The Tick wrote: Given a repository based on a previously fetched version of some software package and having been modified with local changes, what is the best way to update to a more recent version of

Re: [fossil-users] What is the best way to update to a new upstream version

On Tue, Jun 13, 2017 at 02:44:31PM -0500, The Tick wrote: > Thanks, that is what I was looking for. I've set up a test respository and > things look good until I get to the final "merge" step: > > $ f init F.fossil > $ f open F.fossil > $ f add project > $ f commit --tag 1.5 --branch Official > $

Re: [fossil-users] What is the best way to update to a new upstream version

On 6/13/2017 3:05 PM, Joerg Sonnenberger wrote: On Tue, Jun 13, 2017 at 02:44:31PM -0500, The Tick wrote: Thanks, that is what I was looking for. I've set up a test respository and things look good until I get to the final "merge" step: $ f init F.fossil $ f open F.fossil $ f add project $ f

Re: [fossil-users] Unversioned content for distribution

Actually it's not clear what revert does. I removed the file and revert didn't recover it. I created an empty file and revert didn't recover it. (But maybe this is timestamp related, or because I'm on the machine that created the uv file in the first place.) Thanks ../Dave On 14 June 2017 at

Re: [fossil-users] Unversioned content for distribution

I finally got around to this, but I got the following errors on Linux: : ~/Sites/p4ru/kitPJS ; fossil unversioned revert Usage: fossil sync URL : ~/Sites/p4ru/kitPJS ; fossil ver This is fossil version 2.2 [81d7d3f43e] 2017-04-11 20:54:55 UTC : ~/Sites/p4ru/kitPJS ; fossil unversioned list

Re: [fossil-users] Unversioned content for distribution

`fossil uv list` doesn't mention any path information. Does it have path information behind the scenes so that `fossil uv revert` can put the file in the original place? Is there a way to find if any unversioned file has been updated apart from looking at the hash or the date for particular

[fossil-users] progress on fossil 2.0?

Hi, I recently came across this page discussing potential features of a Fossil 2.0, and was wondering if any progress has been made toward any of these: http://www.fossil-scm.org/index.html/info/0e047901c2f4a07d8110f7bb9a94c92b56202700 I am especially interested in: * Partial clones

Re: [fossil-users] src/blob.c : blob_read_from_file overflow int size

Nobody will put big files, but there are logic defects int size; file size is  INT_MAX + 1 then size is negative(INT_MIN) file size is UINT_MAX + 2 then size is 1___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] What is the best way to update to a new upstream version

On Tue, Jun 13, 2017 at 12:17:46PM -0500, The Tick wrote: > Given a repository based on a previously fetched version of some software > package and having been modified with local changes, what is the best way to > update to a more recent version of the upstream package? The best approach is

Re: [fossil-users] src/blob.c : blob_read_from_file overflow int size

[837333fc] Fix the blob_read_from_file thank you. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] What is the best way to update to a new upstream version

Given a repository based on a previously fetched version of some software package and having been modified with local changes, what is the best way to update to a more recent version of the upstream package? A "f addremove" would import the new version but would lose all local changes. What