Re: [fossil-users] Memorable names for ticket IDs

Thus said David Given on Wed, 04 Sep 2013 22:07:32 +0100: > Based on various conversations in the past I have been working on a > semi-interesting features: using mnemonic encoding to turn ticket > hashes into something that humans can remember. What about using the ICAO alphabet? It be e

Re: [fossil-users] Memorable names for ticket IDs

On 2013-09-06 20:11, Ross Berteig wrote: ba-ba-ba-ba 12345678di-ku-poo-wa 74a95e62vu-che-roo-si da39a3ee5e6b4b0d3255bfef95601890afd80709 ghi-le-clo-phoo-roo-to-no-cy-ki-py-frau- phau-bly-sa-fa-bla-cha

Re: [fossil-users] Memorable names for ticket IDs

On 9/5/2013 11:32 PM, Edward Berner wrote: On 9/5/2013 1:39 PM, Doug Franklin wrote: These are going to get long, fast, as someone else already noted. However, in the past I've seen algorithms to generate "random" "words" that are still pronounceable, one character at a time. The trouble here is

Re: [fossil-users] strange `fossil diff ' behaviour

On Wed, Aug 21, 2013 at 8:37 AM, Matt Welland wrote: > Regarding stable numbered tags. How about a script or added feature that > scans the timeline and tags every node in a systematic way similar to what > people might expect from Subversion or similar tools? > > v1.1 -> v1.2 -> v1.3 > \.-

Re: [fossil-users] json timeline segfault on fossils fossil.

Thanks for the quick response! Unfortunately there seems to be another problem: > ./fossil json timeline checkin --limit 10 [snip] { "type":"checkin", "uuid":"f460839cff85d4e4f1360b366bb2858cef1411ea", "is

Re: [fossil-users] Memorable names for ticket IDs

On 5 September 2013 17:41, David Given wrote: > (The alternative is a 2^11 word dictionary, which means coming up with > another 422 suitable words from somewhere, which I don't think is > feasible. The author claims the current dictionary took 300 hours to > compile.) There's an 7776 common word

Re: [fossil-users] json timeline segfault on fossils fossil.

On Fri, Sep 6, 2013 at 7:30 PM, Stestagg wrote: > Isn't it possible to do a unicode-like substitution on invalid characters? > Usually replacing with a '?' Is suitable. > Good point (i am NOT well-versed in encoding-related problems - i am only superficially familiar with them). The byte i'm gett

Re: [fossil-users] json timeline segfault on fossils fossil.

Isn't it possible to do a unicode-like substitution on invalid characters? Usually replacing with a '?' Is suitable. Thanks Steve On 6 Sep 2013 18:17, "Stephan Beal" wrote: > On Fri, Sep 6, 2013 at 6:22 PM, Stephan Beal wrote: > >> On Fri, Sep 6, 2013 at 6:14 PM, Matt Welland wrote: >> >>> Sor

Re: [fossil-users] json timeline segfault on fossils fossil.

On Fri, Sep 6, 2013 at 6:22 PM, Stephan Beal wrote: > On Fri, Sep 6, 2013 at 6:14 PM, Matt Welland wrote: > >> Sorry, I should have specified, this is again with the fossil fossil. >> > > i should have figured that out from the './' prefix. Okay, i've got it > failing here. Thanks for the report

Re: [fossil-users] Memorable names for ticket IDs

On 9/5/2013 2:41 PM, David Given wrote: > I think, without a mathematical proof, that maintaining the ability to > take prefixes of an encoded name will require us to use a dictionary > that fits into a precise number of bits. Truncating the dictionary to > 2^10 entries would be the simplest approa

Re: [fossil-users] json timeline segfault on fossils fossil.

On Fri, Sep 6, 2013 at 5:55 PM, Matt Welland wrote: > > ./fossil json timeline checkin --limit 10 > "comment":"Update to Toni > R\u00f6nkk\u00f6's latest version (1.12.1) of dirent.h [ > http://www.softagalleria.net/dirent.php]";, > fossil: ./src/cson_amalgamat

Re: [fossil-users] json timeline segfault on fossils fossil.

Sorry, I should have specified, this is again with the fossil fossil. On Fri, Sep 6, 2013 at 9:10 AM, Stephan Beal wrote: > On Fri, Sep 6, 2013 at 5:59 PM, Stephan Beal wrote: > >> On Fri, Sep 6, 2013 at 5:55 PM, Matt Welland wrote: >> >>> > ./fossil json timeline checkin --limit 10 >>>

Re: [fossil-users] json timeline segfault on fossils fossil.

On Fri, Sep 6, 2013 at 5:59 PM, Stephan Beal wrote: > On Fri, Sep 6, 2013 at 5:55 PM, Matt Welland wrote: > >> > ./fossil json timeline checkin --limit 10 >> "comment":"Update to Toni >> R\u00f6nkk\u00f6's latest version (1.12.1) of dirent.h [ >> http://www.so

Re: [fossil-users] json timeline segfault on fossils fossil.

On Fri, Sep 6, 2013 at 6:22 PM, Stephan Beal wrote: > On Fri, Sep 6, 2013 at 6:14 PM, Matt Welland wrote: > >> Sorry, I should have specified, this is again with the fossil fossil. >> > > i should have figured that out from the './' prefix. Okay, i've got it > failing here. Thanks for the report

Re: [fossil-users] json timeline segfault on fossils fossil.

On Fri, Sep 6, 2013 at 6:14 PM, Matt Welland wrote: > Sorry, I should have specified, this is again with the fossil fossil. > i should have figured that out from the './' prefix. Okay, i've got it failing here. Thanks for the report - i'll let you know as soon as its fixed. -- - stephan be

Re: [fossil-users] Bug in stash-diff

2013/9/5 Richard Hipp : > The "fossil stash diff" command fails when used with the --tk option. > Bummer. It used to work > > No time to fix it right now, as I'm actually using it on another project. Fixed here ;-) Regards, Jan

Re: [fossil-users] json timeline segfault on fossils fossil.

On Fri, Sep 6, 2013 at 9:30 AM, Stephan Beal wrote: > i suspect that it just happened to finally pick up a record which > triggered this problem > FYI: thanks to a tip from Jan, it is easy to see now that that was indeed the problem. A recent checkin triggered a combination which the json timeli

Re: [fossil-users] json timeline segfault on fossils fossil.

On Fri, Sep 6, 2013 at 9:22 AM, Stephan Beal wrote: > i can reproduce it here as well. i'm working now but will look at it this > evening. That code hasn't been touched in a long time, so this look like an > unintended side effect of other changes. > Nevermind - it was trivial to reproduce, back

Re: [fossil-users] json timeline segfault on fossils fossil.

On Fri, Sep 6, 2013 at 3:39 AM, Ross Berteig wrote: > On 9/5/2013 4:54 PM, Matt Welland wrote: > >> The json timeline seems to have trouble with fossils fossil. >> ./configure --json && make >> ./fossil json timeline checkin --limit 100 >> Segmentation fault >> > > On my clone of fossil's repo, I