Re: [fossil-users] status of sha1 reporting in timeline?

2015-04-28 Thread j. van den hoff
I think I found the answer myself: the relevant checkin seems to be [1fee0377e4] (feb. 11, 2015). sorry for the noise. On Tue, 28 Apr 2015 15:43:43 +0200, j. van den hoff veedeeh...@googlemail.com wrote: I lost track of what exactly has happened w.r.t. to the previously variable-length

Re: [fossil-users] Two trunks?

2015-04-28 Thread bch
For reference, a **rough** comparison (diff't repo) -- this repository does *NOT* have the blob index (suggested by drh) that I manually applied to NetBSD-src: kamloops$ time fossil pull Pull from http://pkgsrc.sonnenberger.org Round-trips: 4 Artifacts sent: 0 received: 177 Pull done, sent:

Re: [fossil-users] Two trunks?

2015-04-28 Thread bch
On 4/27/15, Andy Bradford amb-fos...@bradfords.org wrote: Thus said bch on Mon, 27 Apr 2015 18:33:28 -0700: kamloops$ time fossil pull Pull from http://netbsd.sonnenberger.org Round-trips: 1 Artifacts sent: 0 received: 0 Pull done, sent: 338 received: 1368 ip: 135.28.13.11 1.43

Re: [fossil-users] Two trunks?

2015-04-28 Thread Richard Hipp
On 4/28/15, bch brad.har...@gmail.com wrote: For reference, a **rough** comparison (diff't repo) -- this repository does *NOT* have the blob index (suggested by drh) that I manually applied to NetBSD-src: kamloops$ time fossil pull Pull from http://pkgsrc.sonnenberger.org Round-trips: 4

Re: [fossil-users] Two trunks?

2015-04-28 Thread bch
kamloops$ fossil version This is fossil version 1.32 [440ed5da09] 2015-04-27 23:54:38 UTC And to be clear -- I'm not complaining about that latest pull -- this set of metrics we're collecting and this testing is incredibly low-tech, so it's hard to infer very much from them. I mention that the

Re: [fossil-users] ++ignore option

2015-04-28 Thread Jonathan Hankins
First of all, is this the intended behavior? Secondly, is this common enough to warrant complicating the processing of the existing --ignore option? If yes and yes, then syntax you propose seems unnatural to me. How about: --ignore +CSG (a la NET-SNMP mibdirs handling, maybe allow for -CSG

Re: [fossil-users] ++ignore option

2015-04-28 Thread Ron W
On Tue, Apr 28, 2015 at 3:05 PM, Jonathan Hankins jhank...@homewood.k12.al.us wrote: First of all, is this the intended behavior? The --ignore option behaves as documented. Secondly, is this common enough to warrant complicating the processing of the existing --ignore option? I