Re: [fossil-users] Sixteen-digit event IDs

On Jun 30, 2014 2:20 AM, "Jan Nijtmans" wrote: > > 2014-06-27 23:40 GMT+02:00 Andy Goth : > > How come events are always shown with (at least) sixteen digits on the > > timeline whereas other artifacts are given ten digits? > > > > http://www.fossil-scm.org/fossil/timeline?n=20&y=e > > Just becaus

Re: [fossil-users] Using fossil with Bitbake and the Yocto project

On 6/30/2014 6:53 PM, Ross Berteig wrote: After some effort, I believe I have a working BitBake recipe for cross-compiling fossil in an embedded Linux distribution built by the Yocto Project's BitBake tool. I'll post my recipe for building fossil itself separately, after I've verified that t

Re: [fossil-users] Using fossil with Bitbake and the Yocto project

On Wed, Jul 2, 2014 at 1:19 AM, Ron Wilson wrote: > As for Fossil providing the needed bits to write a plug-in to any given > tool, it is possible to write a plug-in that uses the command line Fossil. > Or, for that matter, a hybrid that uses libfossil for information and > fossil to perform comm

Re: [fossil-users] Sixteen-digit event IDs

On Wed, Jul 2, 2014 at 9:59 AM, Jan Nijtmans wrote: > %S stands for STRINGID already, I see no reason to change it. > > Indeed. i overlooked that. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal

Re: [fossil-users] Sixteen-digit event IDs

2014-06-30 17:12 GMT+02:00 Stephan Beal: > i like it, but how about %U (big U, for UUID)? That one is still available. > > Or maybe %H (hash). Ah, now i see that %S could mean SHA1, so now %S makes > more sense to me. %S stands for STRINGID already, I see no reason to change it.