On Thu, Jun 9, 2016 at 6:19 PM, Warren Young wrote:
> On Jun 9, 2016, at 6:01 PM, Scott Robison wrote:
> >
> > On Thu, Jun 9, 2016 at 2:12 PM, Warren Young wrote:
> > On Jun 9, 2016, at 6:25 AM, rosscann...@fastmail.com wrote:
> > >
> > > The bug:
> > > In lookslike.c, invalid_utf8() returns 'i
On Jun 9, 2016, at 6:01 PM, Scott Robison wrote:
>
> On Thu, Jun 9, 2016 at 2:12 PM, Warren Young wrote:
> On Jun 9, 2016, at 6:25 AM, rosscann...@fastmail.com wrote:
> >
> > The bug:
> > In lookslike.c, invalid_utf8() returns 'invalid' for the input 0xE0,
> > 0xB8, 0x94, which is the Thai chara
Thanks! That patch works for me.
Ross
On Fri, Jun 10, 2016, at 10:01 AM, Scott Robison wrote:
> On Thu, Jun 9, 2016 at 2:12 PM, Warren Young wrote:
>> On Jun 9, 2016, at 6:25 AM, rosscann...@fastmail.com wrote:
>> >
>> > The bug:
>> > In lookslike.c, invalid_utf8() returns 'invalid' for t
On Thu, Jun 9, 2016 at 2:12 PM, Warren Young wrote:
> On Jun 9, 2016, at 6:25 AM, rosscann...@fastmail.com wrote:
> >
> > The bug:
> > In lookslike.c, invalid_utf8() returns 'invalid' for the input 0xE0,
> > 0xB8, 0x94, which is the Thai character 'do dek' (U+0E14).
>
> I took a look at that code
On Jun 9, 2016, at 3:21 PM, rosscann...@fastmail.com wrote:
>
> - it's massive;
It’s also open source under one of the most liberal licenses available. Fossil
could just swipe the one header file it needs. It hasn’t changed since 2005,
so one may presume that it is stable.
> - it has depende
I'm new to this list, so take my opinion lightly, but I would hesitate
to introduce Boost into the fossil build if it's not there already.
Boost adds a long list of complications to any build it's part of:
- it's massive;
- it has dependencies between its modules, so even if you just want a
tiny pa
On 24 May 2016, at 23:42 , Marko Käning wrote:
> My initial point 1) is still open for discussion:
>
>> 1) It would be nice, if private branches were marked in /brlist somehow,
>> preferably
>> by introducing a new column entitled “Private”, or stg similar.
>
> Anyone out there having a
On 6/9/16, Marko Käning wrote:
>
>> (4) Initializing the search index means computing all historical
>> check-in diffs. That might take a while. Figure about 10 check-ins
>> per second. Fossil itself currently has 9506 check-ins, so total
>> initialization time would be 15 minutes. (The "10 ch
On Jun 9, 2016, at 6:25 AM, rosscann...@fastmail.com wrote:
>
> The bug:
> In lookslike.c, invalid_utf8() returns 'invalid' for the input 0xE0,
> 0xB8, 0x94, which is the Thai character 'do dek' (U+0E14).
I took a look at that code, and there is no possibility for it to be correct.
It doesn’t e
On Jun 9, 2016, at 12:23 PM, Clark Christensen wrote:
>
> > Is there a good reason you can’t at least upgrade to the latest point
> > release, 1.34?
>
> I'm not sure what "the latest" offers that I can't live without.
The brief changelog is here:
https://www.fossil-scm.org/index.html/doc/tr
Hi,
On 30 May 2016, at 00:04 , Marko Käning wrote:
> My question was where I find documented which areas are automatically
> pushed/pulled
> and whether one can make it clearer perhaps even in the “fossile config pull
> help”
> or/and something more appropriate.
any feedback on this?
Greets,
On Jun 9, 2016, at 8:40 AM, Andy Bradford wrote:
>
> Hello,
>
> Is it possible to search for actual changes in checkins? For example, if
> I have a repository that has a macro:
>
> #define MACRO { if (x) y; }
>
> Can I search Fossil for all checkins that included replacing code with
> MACRO
Hi Richard,
On 09 Jun 2016, at 17:16 , Richard Hipp wrote:
> I've long thought that this would be a very useful feature to add.
+1
> (1) A full-text index uses roughly 30% as much disk space as the
> content that is being indexed. (This is a mathematical property of
> full-text search - not a
Now that we’re at it…
On 09 Jun 2016, at 21:38 , Warren Young wrote:
> On Jun 9, 2016, at 9:04 AM, Tomek Kott wrote:
>>
>> Any chance that 'bz2' and 'bzip' could be added to the 'official' fossil
>> types? (http://fossil-scm.org/index.html/artifact/aad06cde815b7051?ln=71-288)
>
> If so, then
On Jun 9, 2016, at 9:04 AM, Tomek Kott wrote:
>
> Any chance that 'bz2' and 'bzip' could be added to the 'official' fossil
> types? (http://fossil-scm.org/index.html/artifact/aad06cde815b7051?ln=71-288)
If so, then xz should be added, too. It’s becoming quite popular.
_
Hi Ross,
On 09 Jun 2016, at 14:25 , rosscann...@fastmail.com wrote:
> I've found what seems to be a minor bug in fossil (details below), and
> I'm not sure what the procedure is for reporting it. Can someone
> enlighten me?
you did the right thing: contact this mailing list for help. :)
I asked
> When the most recently modified branch is trunk, then tip and trunk
> happen to be the same. Otherwise, they will point to different
> checkins.Understood. Thanks for the quick answer.
> Is there a good reason you can’t at least upgrade to the latest point
> release, 1.34?
Valid point. I'm
rosscann...@fastmail.com wrote:
>
> The bug:
> In lookslike.c, invalid_utf8() returns 'invalid' for the input 0xE0,
> 0xB8, 0x94, which is the Thai character 'do dek' (U+0E14). This can be
> easily reproduced by trying to commit a file that contains those three
> bytes and nothing else - you will
On 6/9/16, Andy Bradford wrote:
> Hello,
>
> Is it possible to search for actual changes in checkins? For example, if
> I have a repository that has a macro:
>
> #define MACRO { if (x) y; }
>
> Can I search Fossil for all checkins that included replacing code with
> MACRO as a change?
>
Fossil
Hello,
Any chance that 'bz2' and 'bzip' could be added to the 'official' fossil types?
(http://fossil-scm.org/index.html/artifact/aad06cde815b7051?ln=71-288)
Thanks,
Tomek
___
fossil-users mailing list
fossil-
Hello,
Is it possible to search for actual changes in checkins? For example, if
I have a repository that has a macro:
#define MACRO { if (x) y; }
Can I search Fossil for all checkins that included replacing code with
MACRO as a change?
Thanks,
Andy
--
TAI64 timestamp: 400057597ff0
___
Hi,
I've found what seems to be a minor bug in fossil (details below), and
I'm not sure what the procedure is for reporting it. Can someone
enlighten me?
The bug:
In lookslike.c, invalid_utf8() returns 'invalid' for the input 0xE0,
0xB8, 0x94, which is the Thai character 'do dek' (U+0E14). This c
22 matches
Mail list logo
