Re: [fossil-users] This mailing list is now deprecated

[sky5walk]

Ok, obscured my email, but that cat has been out of the bag for years :(

On Sat, Aug 11, 2018 at 2:06 PM,  wrote:

> Doh! Didn't know you could submit a dummy email.
> Even though mail is deprecated, are we still able to change settings?
>
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/options/fossil-users
>
> I asked for my password and no reply?
>
> On Sat, Aug 11, 2018 at 2:01 PM, Andy Bradford  hkgenpbcdpglgfggc...@bradfords.org> wrote:
>
>> Thus said Warren Young on Fri, 10 Aug 2018 08:34:24 -0600:
>>
>> >http://sqlite.1065341.n5.nabble.com/Problems-with-v3-9-0-
>> entry-point-sqlite3-finalize-could-not-be-located-td85005.html#a85069
>> >
>> > You only need to read the first post, not the whole thread.
>> >
>> > Fossil forums prevent that problem.
>>
>> Throwing a rock through an 747's window  is one way to solve the problem
>> of getting a plane  to drop in altitude, but that  doesn't mean it's the
>> best way.
>>
>> The problem described on that link  is about spammers subscribing to the
>> mailing lists and  then sending automated spam to those  who post to the
>> mailing list.
>>
>> We've discussed  this before on  this mailing list and  some suggestions
>> were made, and  I guess this new forum feature  was easier to implement,
>> even if it does make communication less useful.
>>
>> Oddly  enough,  I  haven't  seen  much  of  the  spam  that  people  are
>> complaining about lately---maybe that means  my spam blocking is getting
>> it, or maybe it means the spammers have left?
>>
>> Andy
>> --
>> TAI64 timestamp: 40005b6f2492
>>
>>
>> ___
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] This mailing list is now deprecated

[sky5walk]

Doh! Didn't know you could submit a dummy email.
Even though mail is deprecated, are we still able to change settings?

http://lists.fossil-scm.org:8080/cgi-bin/mailman/options/fossil-users

I asked for my password and no reply?

On Sat, Aug 11, 2018 at 2:01 PM, Andy Bradford <
amb-sendok-1536602477.hkgenpbcdpglgfggc...@bradfords.org> wrote:

> Thus said Warren Young on Fri, 10 Aug 2018 08:34:24 -0600:
>
> >http://sqlite.1065341.n5.nabble.com/Problems-with-v3-9-
> 0-entry-point-sqlite3-finalize-could-not-be-located-td85005.html#a85069
> >
> > You only need to read the first post, not the whole thread.
> >
> > Fossil forums prevent that problem.
>
> Throwing a rock through an 747's window  is one way to solve the problem
> of getting a plane  to drop in altitude, but that  doesn't mean it's the
> best way.
>
> The problem described on that link  is about spammers subscribing to the
> mailing lists and  then sending automated spam to those  who post to the
> mailing list.
>
> We've discussed  this before on  this mailing list and  some suggestions
> were made, and  I guess this new forum feature  was easier to implement,
> even if it does make communication less useful.
>
> Oddly  enough,  I  haven't  seen  much  of  the  spam  that  people  are
> complaining about lately---maybe that means  my spam blocking is getting
> it, or maybe it means the spammers have left?
>
> Andy
> --
> TAI64 timestamp: 40005b6f2492
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] This mailing list is now deprecated

[sky5walk]

Sorry, I re-checked my spam folder and the last one arrived Jul-24.

On Fri, Aug 10, 2018 at 1:35 PM,  wrote:

> Whoa, I still receive spam from this mail list. :(
> While hard to track, I cannot say the same with the forums I use.
> Of course, forums can be hacked and emails exposed, but that is rare and
> targeting richer bounty.
> The fossil forum is a click away. If you resist, then write a crawler to
> retrieve the forum posts you desire.
> Or the forum can push changes to a subscriber.
> I prefer to leave them in the forum.
>
> On Fri, Aug 10, 2018 at 10:34 AM, Warren Young  wrote:
>
>> On Aug 10, 2018, at 7:19 AM, Andy Bradford 
>> wrote:
>> >
>> > Thus said Warren Young on Wed, 08 Aug 2018 11:45:09 -0600:
>> >
>> >>> Will this ever be enabled? I prefer email over web forum posting.
>> >>
>> >> How  would  you  prevent  spammers  from  using  an  email  submission
>> >> mechanism?
>> >
>> > Most mailing list managers prevent  this by only allowing subscribers to
>> > submit  emails.  I cannot  recall  the  last time  I  saw  spam sent  to
>> > fossil-users@lists.fossil-scm.org…
>>
>> That’s not the problem described in the thread I linked you to:
>>
>>http://sqlite.1065341.n5.nabble.com/Problems-with-v3-9-0-
>> entry-point-sqlite3-finalize-could-not-be-located-td85005.html#a85069
>>
>> You only need to read the first post, not the whole thread.
>>
>> Fossil forums prevent that problem.
>>
>> > Gmail supports email aliases.
>>
>> If you’re speaking of the free Gmail product, it only supports the
>> user+...@example.com style, which fools no spammer.  They just strip the
>> +ext bit off.
>>
>> If you mean G Suite, you only get 30 of them per account.  I run the mail
>> server for my personal domains, and I have 240 aliases on my main email
>> account.  You want lots of aliases because it allows you to have unique
>> email addresses for any site whose security you are not entirely certain
>> about.
>>
>> I wish I’d created *more* aliases, in fact, because my real email address
>> gets most of the spam I receive, by far, suggesting that I should have
>> hidden it more often.
>>
>> >> If we don't solve that problem first,  we'll be right back in much the
>> >> same mess as today.
>> >
>> > Replacing a mailing list with a web  forum seems to simply trade one set
>> > of problems  for another.
>>
>> Every choice worth spending thought on has tradeoffs.
>>
>> drh has made his choice.  I don’t think you’re going to sway him on this.
>>
>> > I'm  on dozens  of other public  mailing lists
>> > that get a lot more traffic than Fossil Users does and there seems to be
>> > no problems there…
>>
>> Roughly 80-90% of mail traffic is spam, but that’s not a problem?
>>
>>https://skeptics.stackexchange.com/q/2175
>>
>> > Why don't  we leave  both in place  and see what  people prefer  to use?
>>
>> I made that very suggestion earlier.
>>
>> > Those who  are willing to  live with the  problems that come  with email
>> > will express their preference by continuing to use email.
>>
>> Some of the burdens fall on drh, rather than on the users of the mailing
>> list, so he has some say in how all of this goes.
>>
>> > Is the web forum now moderated?
>>
>> Yes, from day 1.  I am one of the moderators.
>>
>> > Does it help?
>>
>> No spam has made it into the forum blockchain yet.
>>
>> I also haven’t seen anyone attempt to spam the forum.  If it never
>> happens, that’s fine with me.
>> ___
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] This mailing list is now deprecated

[sky5walk]

Whoa, I still receive spam from this mail list. :(
While hard to track, I cannot say the same with the forums I use.
Of course, forums can be hacked and emails exposed, but that is rare and
targeting richer bounty.
The fossil forum is a click away. If you resist, then write a crawler to
retrieve the forum posts you desire.
Or the forum can push changes to a subscriber.
I prefer to leave them in the forum.

On Fri, Aug 10, 2018 at 10:34 AM, Warren Young  wrote:

> On Aug 10, 2018, at 7:19 AM, Andy Bradford 
> wrote:
> >
> > Thus said Warren Young on Wed, 08 Aug 2018 11:45:09 -0600:
> >
> >>> Will this ever be enabled? I prefer email over web forum posting.
> >>
> >> How  would  you  prevent  spammers  from  using  an  email  submission
> >> mechanism?
> >
> > Most mailing list managers prevent  this by only allowing subscribers to
> > submit  emails.  I cannot  recall  the  last time  I  saw  spam sent  to
> > fossil-users@lists.fossil-scm.org…
>
> That’s not the problem described in the thread I linked you to:
>
>http://sqlite.1065341.n5.nabble.com/Problems-with-v3-9-
> 0-entry-point-sqlite3-finalize-could-not-be-located-td85005.html#a85069
>
> You only need to read the first post, not the whole thread.
>
> Fossil forums prevent that problem.
>
> > Gmail supports email aliases.
>
> If you’re speaking of the free Gmail product, it only supports the
> user+...@example.com style, which fools no spammer.  They just strip the
> +ext bit off.
>
> If you mean G Suite, you only get 30 of them per account.  I run the mail
> server for my personal domains, and I have 240 aliases on my main email
> account.  You want lots of aliases because it allows you to have unique
> email addresses for any site whose security you are not entirely certain
> about.
>
> I wish I’d created *more* aliases, in fact, because my real email address
> gets most of the spam I receive, by far, suggesting that I should have
> hidden it more often.
>
> >> If we don't solve that problem first,  we'll be right back in much the
> >> same mess as today.
> >
> > Replacing a mailing list with a web  forum seems to simply trade one set
> > of problems  for another.
>
> Every choice worth spending thought on has tradeoffs.
>
> drh has made his choice.  I don’t think you’re going to sway him on this.
>
> > I'm  on dozens  of other public  mailing lists
> > that get a lot more traffic than Fossil Users does and there seems to be
> > no problems there…
>
> Roughly 80-90% of mail traffic is spam, but that’s not a problem?
>
>https://skeptics.stackexchange.com/q/2175
>
> > Why don't  we leave  both in place  and see what  people prefer  to use?
>
> I made that very suggestion earlier.
>
> > Those who  are willing to  live with the  problems that come  with email
> > will express their preference by continuing to use email.
>
> Some of the burdens fall on drh, rather than on the users of the mailing
> list, so he has some say in how all of this goes.
>
> > Is the web forum now moderated?
>
> Yes, from day 1.  I am one of the moderators.
>
> > Does it help?
>
> No spam has made it into the forum blockchain yet.
>
> I also haven’t seen anyone attempt to spam the forum.  If it never
> happens, that’s fine with me.
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Why no EXE+DLL like SQLite?

[sky5walk]

Hmmm, that sounds like TortoiseFossil?
I would deploy that if available. :)

On Mon, Aug 6, 2018 at 9:42 PM, Gilles  wrote:

> On 07/08/2018 03:21, Ron W wrote:
>
> I never tried Sharp Fossil, but Fuel was a very clunky GUI. I think
> non-programmers would be unwilling to put up with it.
>
> As a simpler alternative, the "GUI" could just be implemented as an
> extension to Windows Explorer, where users would just right-click a folder
> to perform the main tasks provided by Fossil (commit, gdiff, etc.)
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] `unversioned' questions

[sky5walk]

My repo's were built prior to the unversioned feature, so I have not used
this yet. And there is no benefit to migrating my candidate files to
unversioned since their history will remain in the repo without complex
shunning.
But now I am confused by this thread?
If/When I add unversioned files, are their original paths stripped?
Are they stored differently than source code?

../dev/src/myapp/bla*.c
../dev/src/lib/bla*.c
../dev/img/bla*.png<-- unversioned
../dev/exe/myapp.exe   <-- unversioned

Do unversioned files remain in their relative paths at inception?

On Tue, Jun 26, 2018 at 12:58 PM, Andy Goth  wrote:

> I think the next project that needs this feature should write a utility
> script for themselves that uses the uv commands to extract files however
> makes sense for them.  This live experimentation is necessary to figure
> what is needed in practice.  No one is forced to wait for any changes to be
> made to Fossil itself.  One day, a set of best practices (i.e., a vague
> consensus on which compromises and heuristics most people can live with
> most of the time) will emerge, at which point Fossil can adopt them as
> useful defaults, but people should always be able to write new scripts that
> work best for their specific projects.
>
> On 06/26/18 10:31, Richard Hipp wrote:
>
>> My thought was to provide a new setting (perhaps versionable) that
>> specified a directory relative to the root of the check-out into which
>> unversioned files are written whenever one does "fossil update" or
>> "fossil checkout".  If the setting is missing or empty, then Fossil
>> works as it does now.  If you turn on the setting, though, then the
>> unversioned files work just like other files in the check-out, except
>> that Fossil never records their history.
>>
>
> I overall like the idea, but I can envision an endless stream of feature
> creep as people want to do any of the following and more:
>
> - Deal with files having platform-incompatible names (slashes,
> backslashes, drive letters, characters unsupported by the filesystem)
> - Extract only files within certain size ranges
> - Extract only files within certain date ranges
> - Extract only files matching certain glob patterns
> - Update the unversioned files when checking in
> - Get diffs showing which unversioned files have changed
> - Handle new files being added to the unversioned directory
> - Reverse filename mapping done for platform compatibility when checking
> in or adding new unversioned files
> - Selectively check in unversioned files along with the rest of the
> check-in
>
> And on it goes.  All of the above can be done today via shell scripts, so
> projects wanting to experiment are invited to get started right away.
>
> --
> Andy Goth | 
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] `unversioned' questions

[sky5walk]

​Can unversioned files respect their original paths when added?
I have several locations for bitmaps, icons, pdf's, etc.
They do not necessarily reside in an isolated folder.​

Thanks for the new Fossil features!

On Tue, Jun 26, 2018 at 11:31 AM, Richard Hipp  wrote:

> My thought was to provide a new setting (perhaps versionable) that
> specified a directory relative to the root of the check-out into which
> unversioned files are written whenever one does "fossil update" or
> "fossil checkout".  If the setting is missing or empty, then Fossil
> works as it does now.  If you turn on the setting, though, then the
> unversioned files work just like other files in the check-out, except
> that Fossil never records their history.
>
> I'm not sure yet whether or not this is a good idea.  I'll need to
> think about it.
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] What should email notifications look like?

[sky5walk]

Yes, plain text please since hyperlinks will point to richer content.

On Fri, Jun 22, 2018 at 10:46 AM, Marcelo  wrote:

> El vie., 22 jun. 2018 a las 11:09, jungle Boogie ()
> escribió:
>
>>
>> I'd rather have emails delivered in plain text, bypassing
>> html/markdown but that's just my preference.
>>
>
> ​+1 for plain text notifications.
>
> --
>o-=< Marcelo >=-o
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] [sqlite] Mailing list shutting down...

[sky5walk]

 Ha! I can see there are strong opposing opinions for mail vs forum.
I find forums more neatly packaged.
Mailing lists are not easily browsed or searched for relevant terms.
Some run on mail topics are a pain to find the nugget of information
desired.
Forum responses can have votes or kudos assigned which hasten searches.
Still, you will suffer spammers in the forum as bots have figured the user
request pages.
With Fossil's unversioned content, the forum or mail bloat can be minimized.

On Thu, Jun 14, 2018 at 3:59 PM, Warren Young  wrote:

> On Jun 14, 2018, at 1:36 PM, Thomas  wrote:
> >
> > no one wants to see all those in their inbox.
>
> Mailing list messages are easily filtered.
>
> I have one mailbox for each mailing list I subscribe to, and I read
> through the messages in list order, which makes it easy to mentally switch
> gears from one project to the next.
>
> If one project gets out of hand for a while, I can mark only that one
> mailbox as “read” without declaring email bankruptcy on all my other email.
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil v25 x86 exe size on download page <> 2.09MB?

[sky5walk]

Nice, that should be mentioned in the download page.
Since we don't have checksums, the filesize should be known.

On Sat, Feb 17, 2018 at 1:08 PM, Richard Hipp  wrote:

> On 2/17/18, sky5w...@gmail.com  wrote:
> > I built the latest Fossil [01984] using ~\Fossil-01984ee0\win\
> buildmsvc.bat
> > and it creates a 2.92MB exe.
> > The v25 download exe when unzipped = 5.08MB?
> > Are there different compile settings in the download file to make such a
> > larger exe?
> >
>
> The download statically links OpenSSL.
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Fossil v25 x86 exe size on download page <> 2.09MB?

[sky5walk]

I built the latest Fossil [01984] using ~\Fossil-01984ee0\win\buildmsvc.bat
and it creates a 2.92MB exe.
The v25 download exe when unzipped = 5.08MB?
Are there different compile settings in the download file to make such a
larger exe?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] fossil-users Digest, Vol 121, Issue 9

[sky5walk]

I love WinMerge and was unable to trigger the diff from fossil(many
versions ago) as you suggest?
Can you describe how WinMerge is installed and fossil settings that worked
for you?
For now, I cut and paste, which is a drag.

Thanks!

On Tue, Feb 13, 2018 at 1:11 PM, Ron W  wrote:

> On Tue, Feb 13, 2018 at 7:00 AM,  fossil-scm.org> wrote:
>>
>> Date: Tue, 13 Feb 2018 11:42:59 +0100
>> From: Gilles 
>> Subject: Re: [fossil-users] Windows GUI that allows diff between two,
>> revisions?
>>
>> Thanks for the tip. Fuel does have an internal web browser:
>>
>> https://s14.postimg.org/efgcfmwj5/Fossil.Fuel.history.intern
>> al.browser.png
>>
>> If there's no Windows alternative to Fuel, it looks like it's either the
>> web UI or the command line.
>>
>> Is there an easy way to compare two revisions of a file while the
>> repository is closed (ie. not a comparison between a revision in the
>> repo and a live file in the workspace), possibly using WinMerge, so I
>> can easily see what the changes are, check out the latest verison, and
>> copy/paste ?
>>
>
> In the Fossil "web UI", from the timeline, select a commit. Scroll down to
> the file of interest and click on it to show that file's history. In the
> "revision graph" (on the left), click the version you want to compare from
> (the node will turn red), then the version you want to compare to. This
> will display (in the web browser), a differ of the 2 versions.
>
>  To use WinMerge, you need to configure Fossil to use that as the external
> diff (or gdiff) tool. then from the command line:
>
>fossil diff --from VERSION --to VERSION
>
> This will launch WinMerge (with temporary copies) to display the
> differences between the 2 versions. However, Fossil will ignore any changes
> you make in WinMerge.
>
> Until either Fuel is updated (possibly by some one forking it) or some one
> creates a new GUI front end for Fossil (possibly using Electronic or
> similar), this is the best you can get.
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] New "Ardoise" skin

[sky5walk]

​Ardoise is looking very nice. :)
Fix the Tickets 'whiteout' and it should be the default!

On Thu, Jan 11, 2018 at 6:10 PM, Antoine Chavasse 
wrote:

> I have commited a new version in the ardoise skin branch where I have
> reskinned the ticket view, which fixes the overly bright fields there.
>
> I also switched to black text on the ticket report view, so that it is
> readable with the default colors.
>
> On Wed, Jan 10, 2018 at 12:48 AM jungle Boogie 
> wrote:
>
>> On 8 January 2018 at 04:27, Richard Hipp  wrote:
>> > On 1/8/18, Antoine Chavasse  wrote:
>> >> I'm not sure I can fix this from the skin, since the background color
>> for
>> >> ticket reports are configured by the user in the settings.
>> >>
>> >
>> > I might need to enhance Fossil to recognize this situation and make
>> > automatic adjustments to the background color.
>> >
>>
>> If it's not already obvious, the fields on the ticket page are also too
>> bright:
>> https://www.fossil-scm.org/skins/ardoise/tktview?name=c541b6e734
>>
>> Thanks for the new skin, Antoine! I appreciate the work.
>>
>> > --
>> > D. Richard Hipp
>> > d...@sqlite.org
>>
>> --
>> ---
>> inum: 883510009027723
>> sip: jungleboo...@sip2sip.info
>> ___
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] New "Ardoise" skin

[sky5walk]

Yeah, could be old guy eyes and smallish font. But, it is low strain
overall.

On Sun, Jan 7, 2018 at 5:28 PM, Jacob MacDonald  wrote:

> Interesting, I don't notice any contrast issues on my monitor. The font in
> diffs could be a little bigger but the black on green being a problem isn't
> something I picked up on.
>
> On Sun, Jan 7, 2018 at 4:16 PM  wrote:
>
>> Very nice Timeline, but super dark when browsing diff's?
>> The green background needs to be lighter or the font needs brightening.
>>
>> On Sun, Jan 7, 2018 at 4:51 PM, Jacob MacDonald 
>> wrote:
>>
>>> Wow that's a slick skin. Antoine, if you're on the list, top notch work.
>>> Can't wait to get it running in my repos.
>>>
>>> On Sun, Jan 7, 2018 at 3:43 PM Richard Hipp  wrote:
>>>
 The Ardoise skin by Antoine Chavasse is now available on trunk.  You
 can take a test-drive at
 https://www.fossil-scm.org/skins/ardoise/timeline

 --
 D. Richard Hipp
 d...@sqlite.org
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

>>>
>>> ___
>>> fossil-users mailing list
>>> fossil-users@lists.fossil-scm.org
>>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>>
>>>
>> ___
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] New "Ardoise" skin

[sky5walk]

Very nice Timeline, but super dark when browsing diff's?
The green background needs to be lighter or the font needs brightening.

On Sun, Jan 7, 2018 at 4:51 PM, Jacob MacDonald  wrote:

> Wow that's a slick skin. Antoine, if you're on the list, top notch work.
> Can't wait to get it running in my repos.
>
> On Sun, Jan 7, 2018 at 3:43 PM Richard Hipp  wrote:
>
>> The Ardoise skin by Antoine Chavasse is now available on trunk.  You
>> can take a test-drive at
>> https://www.fossil-scm.org/skins/ardoise/timeline
>>
>> --
>> D. Richard Hipp
>> d...@sqlite.org
>> ___
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Timeline comments ignore all newlines AGAIN...

[sky5walk]

Big thanks to Zakero for highlighting subtle CSS/html components necessary
to achieve my desired Compact view.
With the following changes, I now prefer Compact view over Modern.
/* CSS */
span.timelineCompactComment {
  display: block;/*Necessary for margin-top to work.*/
  font-family: Consolas; /*Fixed pitch font.*/
  white-space: pre;  /*Respect newlines and spaces. */
  margin-top: -1em;  /*Shove comment higher in the cell.*/
}
span.timelineEllipsis {
  display: block;/*Necessary for visibilty to work. */
  visibility: hidden;/*Do not show '...'*/
  position: absolute;/*No newline applied to hidden content.*/
}
span.clutter {
  display: block;/*Necessary for visibilty to work. */
  visibility: hidden;/*Do not show 'check-in,user,tags.'*/
  position: absolute;/*No newline applied to hidden content.*/
}

Thanks for Fossil!

On Wed, Dec 20, 2017 at 10:10 AM,  wrote:

> Is this leading and trailing newline in 'timeline[Modern|Compact]Comment'
> intentional or bug?
> Is it necessary to create padding for the borders?
> If so, why can't borders be applied with CSS?
>
> I'm trying to shrink my Timeline text but no idea what CSS strips contents
> of object?
>
> What I see...
> " <-- Why double quote here?
> My multiline comment is here.
> And here...
> " <-- Why double quote here?
>
> What I want...
> "My multiline comment is here.
> And here..."
>
>
> On Tue, Dec 19, 2017 at 1:56 PM,  wrote:
>
>> Ok, using Google Chrome Version 65, I never see CheckBox anywhere within
>> trunk of:
>>   http://fossil-scm.org/index.html/timeline.
>>
>> "Johan"
>> Leaf check-in: a6c5a462 user: drh tags: trunk
>> When you select that element, you should see, in one of the "Developer's
>> Tools" frames, the definition for the selected element's CSS class(es):
>>
>> (CB = CheckBox)
>>
>> .timelineModernDetail{
>>   CB: font-size: 80%;
>>   CB: text-align: right;
>>   CB: float: right;
>>   CB: opacity: 0.75;
>>   CB: margin-top: 0.5em;
>>   CB: margin-left: 1em;
>> }
>>
>> But I do see the light. The Style was not 'text-align: left', but 'float:
>> left'.
>> span.timelineModernDetail {
>>   float: left;
>> }
>>
>> Even with this insight, I cannot shift the 'timelineModernComment' text
>> up because it is mysteriously surrounded with a leading and trailing
>> newline?
>>
>> What I see...
>> "  <-- Why is the double quote here?
>> My multiline comment is here.
>> And here...
>> "  <-- Why is the double quote here?
>>
>> What I want...
>> "My multiline comment is here.
>> And here..."
>>
>>
>> Thanks for the 'teach a man to fish' pointers.
>>
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Timeline comments ignore all newlines AGAIN...

[sky5walk]

Is this leading and trailing newline in 'timeline[Modern|Compact]Comment'
intentional or bug?
Is it necessary to create padding for the borders?
If so, why can't borders be applied with CSS?

I'm trying to shrink my Timeline text but no idea what CSS strips contents
of object?

What I see...
" <-- Why double quote here?
My multiline comment is here.
And here...
" <-- Why double quote here?

What I want...
"My multiline comment is here.
And here..."


On Tue, Dec 19, 2017 at 1:56 PM,  wrote:

> Ok, using Google Chrome Version 65, I never see CheckBox anywhere within
> trunk of:
>   http://fossil-scm.org/index.html/timeline.
>
> "Johan"
> Leaf check-in: a6c5a462 user: drh tags: trunk
> When you select that element, you should see, in one of the "Developer's
> Tools" frames, the definition for the selected element's CSS class(es):
>
> (CB = CheckBox)
>
> .timelineModernDetail{
>   CB: font-size: 80%;
>   CB: text-align: right;
>   CB: float: right;
>   CB: opacity: 0.75;
>   CB: margin-top: 0.5em;
>   CB: margin-left: 1em;
> }
>
> But I do see the light. The Style was not 'text-align: left', but 'float:
> left'.
> span.timelineModernDetail {
>   float: left;
> }
>
> Even with this insight, I cannot shift the 'timelineModernComment' text up
> because it is mysteriously surrounded with a leading and trailing newline?
>
> What I see...
> "  <-- Why is the double quote here?
> My multiline comment is here.
> And here...
> "  <-- Why is the double quote here?
>
> What I want...
> "My multiline comment is here.
> And here..."
>
>
> Thanks for the 'teach a man to fish' pointers.
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Timeline comments ignore all newlines AGAIN...

[sky5walk]

Ok, using Google Chrome Version 65, I never see CheckBox anywhere within
trunk of:
  http://fossil-scm.org/index.html/timeline.

"Johan"
Leaf check-in: a6c5a462 user: drh tags: trunk
When you select that element, you should see, in one of the "Developer's
Tools" frames, the definition for the selected element's CSS class(es):

(CB = CheckBox)

.timelineModernDetail{
  CB: font-size: 80%;
  CB: text-align: right;
  CB: float: right;
  CB: opacity: 0.75;
  CB: margin-top: 0.5em;
  CB: margin-left: 1em;
}

But I do see the light. The Style was not 'text-align: left', but 'float:
left'.
span.timelineModernDetail {
  float: left;
}

Even with this insight, I cannot shift the 'timelineModernComment' text up
because it is mysteriously surrounded with a leading and trailing newline?

What I see...
"  <-- Why is the double quote here?
My multiline comment is here.
And here...
"  <-- Why is the double quote here?

What I want...
"My multiline comment is here.
And here..."


Thanks for the 'teach a man to fish' pointers.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Timeline comments ignore all newlines AGAIN...

[sky5walk]

Thanks for the holiday reading material Johan!
This helps a lot. Every time I dabble in HTML, it only makes it to short
term memory. :(
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Timeline comments ignore all newlines AGAIN...

[sky5walk]

Came back to this after dinner.
The introduction of new Timeline classes(Modern,Compact,Verbose,Columnar)
means there is no catch-all for timelineComment.
So, I cut and paste in the CSS for each possible case.
/* Enable timeline comments to respect linefeeds. */
span.timelineModernComment {
  font-family: Consolas;
  white-space: pre;
}
And I had to check both boxes before clicking Publish button.
  [x] Skin draft1 has been tested and found ready for production.
  [x] The current skin should be overwritten with draft1.
  {Publish} <-- Click button to update CSS in use.
~~
Having done that, I have my newline comments.
But, I now see issues with 'Compact' being not very. The ellipsis is on its
own line.
'Modern' jumps out as the most clean, but it has a leading blank line I'd
like to remove.

How can I force the 'timelineModernDetail' contents to be centered or
left-justified?
And prevent the empty leading line in timelineModernComment?

Thanks for Fossil!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Timeline comments ignore all newlines AGAIN...

[sky5walk]

Ok, I clicked and clacked with the Publish button and I am getting changes.
Before, I could edit my CSS and the page would reflect the changes
immediately.
I now think I have a corrupt CSS, since I lost my menus and header/footer.
I'll edit the default CSS and re-insert the 'white-space: pre;' items.

On Mon, Dec 18, 2017 at 12:10 PM,  wrote:

> From my previous CSS:
> /* Enable Check-in comments to respect linefeeds. */
> span.checkinComment {
>   font-family: Consolas;
>   white-space: pre;
> }
> /* Enable timeline comments to respect linefeeds. */
> span.timelineComment {
>   font-family: Consolas;
>   white-space: pre;
> }
> /* This was mentioned in the mail archives, but no help.
> span.timelineTableCell {
>   font-family: Consolas;
>   white-space: pre;
> }*/
>
> And my Timeline options have no effect?
> [±] Plaintext comments on timelines
> [±] Allow block-markup in timeline
>
> On Mon, Dec 18, 2017 at 12:03 PM, Andy Bradford  lodfjffpjfhkiikmb...@bradfords.org> wrote:
>
>> Thus said sky5w...@gmail.com on Mon, 18 Dec 2017 11:17:49 -0500:
>>
>> > I just  compiled fossil  version 2.5 [a6c5a4620a]  2017-12-18 02:06:40
>> > UTC under  Windows 10 and nothing(every  view option + CSS  + Timeline
>> > option) I try shows my commit comment[CR][LF]'s.
>>
>> What CSS and Timeline option are you talking about?
>>
>> Are you talking about this Timeline setting in /setup_timeline?
>>
>>  Plaintext comments on timelines
>>
>> In timeline displays, check-in comments are displayed literally,
>> without  any wiki  or  HTML interpretation.  Use  CSS to  change
>> display  formatting features  such  as  fonts and  line-wrapping
>> behavior. (Property: "timeline-plaintext")
>>
>> If so, what CSS are you using?
>>
>> Thanks,
>>
>> Andy
>> --
>> TAI64 timestamp: 40005a37f512
>>
>>
>>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Timeline comments ignore all newlines AGAIN...

[sky5walk]

I just compiled fossil version 2.5 [a6c5a4620a] 2017-12-18 02:06:40 UTC
under Windows 10 and nothing(every view option + CSS + Timeline option) I
try shows my commit comment[CR][LF]'s.
Any ideas?
My check-in comments are intentionally multi-line. Stripping the newlines
renders my timeline as noise.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Metadata in Timeline Verbose View

[sky5walk]

Wow, you are fast. Back to 1 pair ().

On Dec 11, 2017 8:13 PM, "Richard Hipp"  wrote:

> On 12/11/17, sky5w...@gmail.com  wrote:
> > Compact view now has double ((parentheses)) ??
>
> Did you press "Reload"?  Can you send me a link to the page you are
> viewing?
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Metadata in Timeline Verbose View

[sky5walk]

Compact view now has double ((parentheses)) ??

On Dec 11, 2017 7:03 PM, "Richard Hipp"  wrote:

> A new version of Fossil is up with some minor UI tweaks:
>
> (1) No more box around comments in the Modern and Columnar views.
> Instead, the background color is a light gray.
>
> (2) The details of each entry are shown inside parentheses in the
> Verbose and Compact views.
>
> Please continue to provide feedback.
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] A-B comparison of proposed timeline changes

[sky5walk]

I agree. Why does the [brief-hash] need to be a hyperlink and bracketed
when the Timeline time stamp has the same link?

On Tue, Dec 5, 2017 at 9:30 AM, Reimer Behrends  wrote:

> Richard Hipp wrote:
>
>> Which is better?
>>
>>A:  https://www.fossil-scm.org/a/timeline
>>B:  https://www.fossil-scm.org/b/timeline
>>
>
> I don't see much of a difference, to be honest (but that may be because
> I'm late to the party and the layouts have changed during the past days).
> The modern/normal/columnar views all seem to consume a lot of screen real
> estate for my taste.
>
> I'll add that my biggest issue with the timeline UI is the presentation of
> check-in links. You cannot copy them without the surrounding brackets,
> which means that you cannot paste them into the command line without
> editing, or first clicking through the link and then using the entire hash.
> This is exacerbated by the problem that on the command line, `fossil
> timeline` is very limited compared to what the web UI offers, so for a lot
> of use cases, you're forced to use the web interface.
>
> Reimer Behrends
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] A-B comparison of proposed timeline changes

[sky5walk]

Focusing on the Compact view:
Is there any chance to limit the click action to just the ellipses?
And to revert, click on the added content, Ex. "check-in:" or "user:".
As others mentioned, it is annoying when selecting text from the comments
to have the background action.

On Wed, Nov 29, 2017 at 10:50 AM, Warren Young  wrote:

> On Nov 29, 2017, at 8:26 AM, Richard Hipp  wrote:
> >
> > On 11/29/17, Warren Young  wrote:
> >>
> >>https://imgur.com/a/TEWjA
> >
> > I think we'd like the selection mechanism to somehow highlight the
> > entire row
>
> I don’t think it really helps, but this gets you part of the way there:
>
> tr.timelineSelected td.timelineModernCell {
>   border-width: 0;
>   border-radius: 0;
> }
>
> For some reason, border-radius and the box-shadow effect don’t combine
> well on  as they do with , at least with Chrome.
>
> You can’t make the white gaps go away without collapsing borders
> throughout the table, which would remove the white gaps between colored
> rows, too.
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] More timeline changes

[sky5walk]

I will try smallest scaling of the ellipsis, if it really must remain...
And I can live with .timelineEllipsis { display: 'none'; }, since the
Advanced button will override if I want extra info.
Thanks for the options.



On Sat, Nov 25, 2017 at 9:52 PM, David Mason  wrote:

> 
>   function cancelProp(event){
>  if (event.stopPropagation) {event.stopPropagation()} //w3c
> else {event.cancelBubble = true } // ie
>   }
> 
> 
>   http://google.ca; onclick="cancelProp(event)" title=" ">
> google
>   
>   blah blah
> 
>
> Suppressing the title on the link is tricky the above works on
> Chrome/Firefox but shows a space on IE/Safari - see:
> https://stackoverflow.com/questions/5881954/html-stop-child-elements-from-
> inheriting-parents-title-attribute but you might have a useful title to
> give it.
>
> ../Dave
>
> On 25 November 2017 at 20:47, Richard Hipp  wrote:
>
>> On 11/25/17, David Mason  wrote:
>> >
>> > When I did that, I made clicking on anywhere in that div expand it.
>> >
>>
>> I've done that in the latest.  Actually, I made it click-to-toggle.
>> That seems to work a lot better than trying to click on the ellipsis.
>>
>> But there is a subtle problem.  For timeline comments that contain a
>> hyperlink (ex: https://www.sqlite.org/srcx/timeline?c=b016c28f) if I
>> click on the hyperlink, it first toggles the detail on/off before it
>> takes the hyperlink.  Do you have suggestions on how I can disable the
>> "onclick" on the outer  when one clicks inside an inner ?
>> --
>> D. Richard Hipp
>> d...@sqlite.org
>>
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] More timeline changes

[sky5walk]

Ok, the current behavior is cool, but renders the ellipses superfluous.
Clicking anywhere in a line expands/contracts the info.
Any chance to drop the many many ⋯'s after all my comments?

On Sat, Nov 25, 2017 at 8:47 PM, Richard Hipp  wrote:

> On 11/25/17, David Mason  wrote:
> >
> > When I did that, I made clicking on anywhere in that div expand it.
> >
>
> I've done that in the latest.  Actually, I made it click-to-toggle.
> That seems to work a lot better than trying to click on the ellipsis.
>
> But there is a subtle problem.  For timeline comments that contain a
> hyperlink (ex: https://www.sqlite.org/srcx/timeline?c=b016c28f) if I
> click on the hyperlink, it first toggles the detail on/off before it
> takes the hyperlink.  Do you have suggestions on how I can disable the
> "onclick" on the outer  when one clicks inside an inner ?
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] More timeline changes

[sky5walk]

Man, are those ellipses absolutely necessary?
(So close with the previous uncluttered timeline.)
Is it possible to make the 1st word/sentence of the checkin comment a
hyperlink to the extra info?

On Sat, Nov 25, 2017 at 5:51 PM, Marc Simpson  wrote:

> One other (potential) problem: without the hash prefix, descriptions
> run together.
>
> Example: http://www.sqlite.org/src/timeline, 2017-11-24. The graph
> nodes are flushed to the left, so descriptions appear as:
>
>   Add the "^" syntax from fts3/4 to fts5. ...
>   Enhance the configure script to detect zLib. ...
>
> It's not immediately clear that these are separate commits given the
> amount of horizontal space; adding a bit more vertical padding or
> boxing descriptions (perhaps with alternating colours) might help?
>
> Personally, I prefer seeing the short hash before each description
> (perhaps this could be an option in the Advanced view?).
>
> /M
>
> On Sat, Nov 25, 2017 at 2:06 PM, Tony Papadimitriou  wrote:
> > The idea looks very good to me.  But the ellipses are indeed barely
> visible.
> > How about replacing ... with [*] as a generic (foot)note mark?
> >
> > -Original Message- From: Richard Hipp
> > Timelines now come up in Basic mode, which means only the check-in
> > comment shows.  There are ellipses at the end of each comment.  If you
> > click on the ellipsis for one comment, it expands the (detail) section
> > for that one timeline entry.
> >
> > The ellipses at the ends of comments in basic mode are barely visible.
> >
> > D. Richard Hipp
> >
> >
> > ___
> > fossil-users mailing list
> > fossil-users@lists.fossil-scm.org
> > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] More timeline changes

[sky5walk]

"​(2) Decluttered should be the default."
I agree clutter should not be default?​
I would drop that term altogether.

On Sat, Nov 25, 2017 at 8:47 AM, Richard Hipp  wrote:

> In the latest code on https://www.fossil-scm.org/fossil/timeline and
> at https://sqlite.org/srcx/timeline has a "Declutter" button on the
> sub-menu bar to simplify the screen.  In the simplified timeline,
> there is a "Details" button to get all the details back again.
>
> I'm not done with this interface improvement push.  Here are my
> short-term plans:
>
> (1) Right now, pressing "Declutter" or "Details" is a server
> round-trip.  I think it would better to handle this using javascript.
>
> (2) Decluttered should be the default.  Currently Details is the
> default.  I spent a lot of time experimenting last night, and what I
> found myself doing every time I encountered a timeline was immediately
> pressing the "Declutter" button to get a high-level overview of the
> graph, then clicking on "Details" if I wanted to see more.  From that
> experience, I think coming up in Decluttered mode would be a much
> better approach.
>
> (3) Details/Declutter for the entire graph is good and should be kept.
> But it would be even better to be able to see the details of
> individual timeline entries.  I'm thinking that timelines come up in
> decluttered mode (showing only the check-in comment for each entry)
> but with ellipses or some other small icon at the end of each comment
> that you can click on to expand the details.
>
> You can help!  Send me your ideas of what you think timelines should
> look like.  Even better:  send me mock-ups.  Static HTML pages that
> you have hand-edited will be fine - just be sure to include the CSS,
> or better, put all the CSS in-line on your hand-edited mockup.
>
> You can also keep experimenting with the code I have on-line and send
> me your complaints and suggestions for improvement.
>
> Web developers - help me with this:  For item (3) above, how can I
> make the ellipsis or icon to "show more detail" configurable using
> CSS?  What's the best way to handle that so that people can customize
> the look for various skins?
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] A-B comparison of proposed timeline changes

[sky5walk]

Wow, #5 is super clean and easy on the eyes!
And #12 is interesting if I can see it with Per-Item Time Format = (off)?

Thanks for the changes!

On Fri, Nov 24, 2017 at 7:12 PM, Richard Hipp  wrote:

> On 11/24/17, Zakero  wrote:
> >
> > tldr; This new change of the timeline makes it harder to find useful
> links.
> >
>
> There is now a per-repository configuration option under
> Setup/Timeline that lets you choose which timeline format you prefer.
>
> https://www.fossil-scm.org/fossil/ is currently configured so that
> when you click on the "Timeline" menu, you get
> https://www.fossil-scm.org/fossil/timeline?basic - the "basic" query
> parameter declutters the display as much as possible to be friendly to
> newbies.  You can change this on your repos by searching for
> "/timeline?basic" in your "Header" configuration and omitting the
> query parameter.
>
> There is an undocumented query parameter on /timeline that lets you
> experiment with different formatting options without having to change
> the configuration.
>
>https://www.fossil-scm.org/fossil/timeline?commentformat=1
>https://www.fossil-scm.org/fossil/timeline?commentformat=2
>https://www.fossil-scm.org/fossil/timeline?commentformat=3
>https://www.fossil-scm.org/fossil/timeline?commentformat=4
>https://www.fossil-scm.org/fossil/timeline?commentformat=5
>https://www.fossil-scm.org/fossil/timeline?commentformat=12
>
> The "basic" query parameter simply forced commentformat=5 and then
> disables a lot of the complex submenu controls, replacing them all
> with an "Advanced" button that turns "basic" off.
>
> Other values for commentformat=N are possible, but are reserved for
> future expansion.
>
> Thanks to everyone who contributed comments!  All suggestions were
> useful, even those that I did not implement.  It is important to have
> lots of ideas in circulation.
>
> One thing I learned from this exercise is that no two people want the
> timeline to look the same way.   Consensus is not a possibility here.
> There is too much diversity of opinion. Therefore, I had to exercise
> my authority as the BDFL and pick one particular behavior for the
> canonical Fossil repo and to be the default.  You are welcomed to pick
> a different behavior for your own repositories, since it is now
> configurable.
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] A-B comparison of proposed timeline changes

[sky5walk]

I understand the need for links, but do users really need truncated hashes
for every line?
Can the link be applied more subtly?
Can there be a similar "quiet" setting for the Timeline like *Per-Item Time
Format = (off) *to conserve space?
My commits prepend a simple timestamp in the comment and multiline text for
more immediate descriptions right up front.
Having this tail every entry -> (check-in: [4dfa592f]
 user: drh

 tags: trunk
)
<-
makes the timeline quite busy.

Thanks for Fossil!

On Fri, Nov 24, 2017 at 11:27 AM, Richard Hipp  wrote:

> On 11/24/17, bch  wrote:
> >>
> >>   (1)  The "details" section is shown on a separate line below the
> >> check-in comment.
> >>   (2)  The "details" are in the same font-color as the comment-text
> >> but have a slightly reduced font size.
> >>
> >
> > I don’t see that reflected on the link.
>
> Those are CSS changes.  So you will need to press "Reload" in your
> browser, possibly multiple times if you use Chrome, before you will be
> able to see the changes.
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] FOSSIL crash when searching WIKI from GUI

[sky5walk]

Only these items:

 *Search Check-in Comments*
 *Search Documents*
 *Search Tickets*
 *Search Wiki*
 *Search Tech Notes*

On Sat, Nov 18, 2017 at 12:02 PM, Richard Hipp  wrote:

> On 11/18/17, sky5w...@gmail.com  wrote:
> > Confirmed on Windows 10 Pro, fossil version 2.4 [a0001dcf57] 2017-11-03
> > 09:29:29 UTC.
> > My crash happened in a Timeline search for '.', not that I would ever do
> > that. :)
>
> How do you have search configured on the system where this is happening?
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] FOSSIL crash when searching WIKI from GUI

[sky5walk]

Confirmed on Windows 10 Pro, fossil version 2.4 [a0001dcf57] 2017-11-03
09:29:29 UTC.
My crash happened in a Timeline search for '.', not that I would ever do
that. :)

On Fri, Nov 17, 2017 at 6:04 PM, Tony Papadimitriou  wrote:

> I forgot to mention this is a on Windows machine (in case it matters.)
>
> It happens with whatever repo I try (including the current sqlite3 and
> fossil).
> But, you need to type the dot at the search box, not with the URL.
>
> So, go Admin/Search and enable Search Wiki (apply changes), then go to the
> Wiki tab and enter a dot in the search box and press the button.
>
> It also happens with Ticket Search (and I didn't try the others) so I
> suppose it's a common issue for all searches done this way.
>
> -Original Message- From: Richard Hipp
>
> On 11/17/17, Tony Papadimitriou  wrote:
>
>> Just to report an issue I noticed today.
>>
>> If I put just a dot [.] in the GUI Wiki/Search box and press ‘Search Wiki’
>> it crashes.
>>
>> This happens both with v1.37 that I normally use, and with version 2.4
>> [a0001dcf57] 2017-11-03 09:29:29 UTC
>>
>>
> Seems to work ok for me.  https://www.fossil-scm.org/fossil/wiki?s=.
>
> Can you point me to a specific example that fails?
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Unversioned content for distribution

[sky5walk]

Great, I'll give that a try.

On Wed, May 10, 2017 at 4:17 PM, Richard Hipp  wrote:

> On 5/10/17, sky5w...@gmail.com  wrote:
> > Cool,
> > Does this behave identically if I have:
> >   http://localhost:8082/setup_settings
> > [±] autosync //<-- ON or OFF?
> >
>
> Yes.  Unversioned content does not autosync.  You have to explicitly
> runt "fossil uv sync".
>
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Unversioned content for distribution

[sky5walk]

Cool,
Does this behave identically if I have:
  http://localhost:8082/setup_settings
[±] autosync //<-- ON or OFF?

Thanks.

On Wed, May 10, 2017 at 9:34 AM, David Mason  wrote:

> Perfect! I knew it would be easy.
>
> Thanks
>
> On 10 May 2017 at 07:04, Richard Hipp  wrote:
>
>> On 5/10/17, David Mason  wrote:
>> > I have a fossil repo and in it I have a file foo.js that is generated
>> by my
>> > build process - so I don't want it versioned. But I *do* want it
>> > distributed, and want it referencable from foo.html - which *is*
>> versioned.
>> > foo.html and foo.js are *not* served by fossil, but by a simple apache
>> or
>> > nginx server.
>> >
>> > So in my working directory I create foo.js and then do what to get it
>> moved
>> > to the master fossil repo.
>>
>> fossil uv add foo.js
>> fossil uv sync
>>
>>
>> > Then on my production machine I do what command
>> > to get the current version of foo.js from the master fossil repo?
>>
>> fossil uv sync
>> fossil uv export foo.js foo.js
>> OR:  fossil uv cat foo.js >foo.js
>>
>> >
>> > I'm sure it's easy, but the documentation does not give me guidance on
>> this
>> > simple use-case.
>> >
>> > Thanks  ../Dave
>> >
>>
>>
>> --
>> D. Richard Hipp
>> d...@sqlite.org
>> ___
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Couple of beginner questions

[sky5walk]

the.tick - "Where and how would I use the above?"

Browse a fossil ui of your repo and edit the skin - CSS page:
http://localhost:8082/setup_skinedit?w=0

On Wed, Mar 29, 2017 at 5:18 PM, The Tick  wrote:

> On 3/29/2017 4:03 PM, sky5w...@gmail.com wrote:
>
>> Doh! It was my CSS. I was using a test repo without my modified CSS. Now
>> it works.
>> I think this is the 2nd time I tripped on this. :(
>>
>> // from CSS //
>> /* THIS DOES NOT WORK - Enable Check-in comments to respect linefeeds. */
>> span.checkinComment {
>>   font-family: Consolas;
>>   white-space: pre;
>> }
>> /* THIS WORKS - Enable timeline comments to respect linefeeds. */
>> span.timelineComment {
>>   font-family: Consolas;
>>   white-space: pre;
>> }
>>
>
> Where and how would I use the above?
>
>
>> @the.tick - With UTF-8(±BOM) source files, I can't reproduce your
>> problem. Win10 x64, Fossil v2.1.
>>
>
> I'm on win7x64. Both Active State's Tcl 8.6.4 and a compiled 8.6.6
> (msys2's x64 gcc) barf on the 'bom' at the beginning of a .tcl source file.
> I compiled fossil from the 2.1 source I downloaded around 3/13. That
> version of fossil ignores newlines in my commit text -- I need to look into
> this markup thing.
>
> On Wed, Mar 29, 2017 at 4:04 PM, Richard Hipp > > wrote:
>>
>> On 3/29/17, sky5w...@gmail.com 
>> > wrote:
>> >
>> > Side note:
>> > I have all Timeline Display Preferences unchecked and my v2.1
>> Timeline does
>> > not respect new lines in my check-in comment?
>> > v1.37 showed newlines in the Timeline for identical setup.
>> > Is this intentional change?
>> >
>>
>> No.  Can you show us a test case?
>> --
>> D. Richard Hipp
>> d...@sqlite.org 
>>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Couple of beginner questions

[sky5walk]

Doh! It was my CSS. I was using a test repo without my modified CSS. Now it
works.
I think this is the 2nd time I tripped on this. :(

// from CSS //
/* THIS DOES NOT WORK - Enable Check-in comments to respect linefeeds. */
span.checkinComment {
  font-family: Consolas;
  white-space: pre;
}
/* THIS WORKS - Enable timeline comments to respect linefeeds. */
span.timelineComment {
  font-family: Consolas;
  white-space: pre;
}

@the.tick - With UTF-8(±BOM) source files, I can't reproduce your problem.
Win10 x64, Fossil v2.1.

Thanks!

On Wed, Mar 29, 2017 at 4:04 PM, Richard Hipp  wrote:

> On 3/29/17, sky5w...@gmail.com  wrote:
> >
> > Side note:
> > I have all Timeline Display Preferences unchecked and my v2.1 Timeline
> does
> > not respect new lines in my check-in comment?
> > v1.37 showed newlines in the Timeline for identical setup.
> > Is this intentional change?
> >
>
> No.  Can you show us a test case?
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Couple of beginner questions

[sky5walk]

Yes, change your text files to UTF-8 with BOM(unsure without BOM) and
Fossil respects °, ±, ©, ®, special characters.

Side note:
I have all Timeline Display Preferences unchecked and my v2.1 Timeline does
not respect new lines in my check-in comment?
v1.37 showed newlines in the Timeline for identical setup.
Is this intentional change?

Thanks

On Wed, Mar 29, 2017 at 3:36 PM, Richard Hipp  wrote:

> On 3/29/17, The Tick  wrote:
> > 1) When I did a commit, I formatted the commit message very nicely.
> > After the commit, it's just a big blob of text. That certainly defeats
> > the purpose of making a commit message of any detail.
> >
> > What is the standard practice with this? Keeping a separate
> > "changelog.txt" where the details are listed? Now I've got another file
> > to keep accurate?
>
> The default formatting for comments is Wiki markup.  You can change
> this for each repo using the Admin/Timeline menu.
>
> Fossil users usually do not follow the Git convention of providing a
> one-line description on the check-in, followed by a blank line and
> logs of additional comments.  That just never has caught on.  You can
> do that, though.  Notice on the Admin/Timeline page the "Truncate
> Comment At First Blank Line" setting.
>
> >
> > 2) My source has a couple of characters like copyright and the
> > multiplication 'x' and I get this message from fossil:
> >
> > ./Guide.tcl contains invalid UTF-8. Use --no-warnings or the
> > "encoding-glob" setting to disable this warning.
> > Commit anyhow (a=all/c=convert/y/N)?
> >
> > I set encoding-glob to *.tcl so now the message goes away.
> >
> > I've read this:
> > http://fossil-users.fossil-scm.narkive.com/6Ci1qs0J/file-
> contains-invalid-utf-8-but-is-not-utf-8
> >
> > As that post mentioned, my © symbol remains but fossil shows the file
> > with a black ? in place of the ©.
> >
> > I use gvim and switching to a different editor is something that will
> > never happen.
>
> Fossil will use UTF-8.  So if you want Fossil to display the 
> correctly, you'll want to insert it as UTF-8.  Apparently gvim is
> using some codepage of some kind.  So if you want  to display in
> gvim, you have to use the the appropriate codepage value.  These are
> incompatible requirements.  You have to choose one or the other.
>
> Most of the world is using UTF-8 now.
>
> >
> > I tried saying 'c' for convert and fossil made a new file with "real
> > utf-8" characters in the place of the originals.
> >
> > The copyright symbol is something that I really want in the source file
> > -- it's in a comment but that is beside the point. It needs to show as a
> > real copyright symbol when the file is edited >and< viewed. As far as I
> > know, gvim does not have a way to convert the goofy "real utf-8"
> > sequence to a copyright symbol so I cannot see the © when I edit the
> > file >nor can I insert a real utf-8 copyright symbol<. Also neither
> > notepad nor another file viewer shows the "real utf-8" copyright symbol
> > correctly in a "converted" file.
> >
> > Is there any solution to this?
> >
>
> You could use the three-character ASCII sequence "(C)" instead of the
> one-character  symbol.  Or, you can simply spell out the word
> "Copyright".  I do the latter.
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] setting hash-policy via web UI

[sky5walk]

Thanks for the detailed replies.
I will make the leap to v2.1 shortly.

Thanks for Fossils-ha!

On Thu, Mar 9, 2017 at 7:02 PM, Warren Young  wrote:

> On Mar 9, 2017, at 3:11 PM, sky5w...@gmail.com wrote:
> >
> > I am asking since I would prefer to create new repo's with sha3 now
> using fossil 2.1.
>
> That’s what you will get by default.  You have to go out of your way with
> Fossil 2.1+ to get a new SHA-1 based repo.
>
> > Then figure how to update/rebuild my older repo's using sha3?
>
> Upgrade to Fossil 2.1+, then say “fossil set hash-policy sha3” in each
> repo where you want new content to be hashed with SHA-3.
>
> If all your local repos either need to be converted or are clones of
> remote repos that will soon be shipping SHA-3 hashed artifacts (e.g. Fossil
> itself), you can say “fossil all set hash-policy sha3” instead, upgrading
> them all at once.
>
> Fossil 2.1+ will purposely not rewrite all the old artifacts with SHA-3
> hashes because that would break any intra-repository links, such as between
> checkin comments and tickets, wiki articles and mentioned checkins, etc.
> Only new content gets hashed with SHA-3 once its hash policy has been
> switched to SHA-3, whether explicitly or implicitly.
>
> See the “firewall” thread if you’re worried about the consequences of
> leaving the old content hashed with SHA-1.  (Executive summary: relax.)
>
> Maybe someone will write a tool that rebuilds an old repo with all-SHA-3
> for those who aren’t worried about the intra-repository links.
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] setting hash-policy via web UI

[sky5walk]

Confused a bit reading this...will Fossil 2.1 default to sha3 or sha1
hardened?http://www.fossil-scm.org/index.html/doc/trunk/www/hashpolicy.wiki"A
Pure SHA3 FutureAt some point in the future, years from now, after
everybody has finally upgraded to Fossil 2.0 or later, the default hash
policy will probably change to "sha3", or maybe even "shun-sha1". By the
time that happens, you will probably already be using SHA3 on all your
projects and so you are unlikely to notice."

I am asking since I would prefer to create new repo's with sha3 now using
fossil 2.1.
Then figure how to update/rebuild my older repo's using sha3?
Is that even possible?


On Thu, Mar 9, 2017 at 5:03 PM, Warren Young  wrote:

> On Mar 9, 2017, at 3:00 PM, Warren Young  wrote:
> >
> > Maybe then just a notice in Admin > Configuration or similar: “Hey, you
> know you’ve got a repo that Fossil 1.x can’t read, right?  Just checking.”
>
> It could be conditional based on the repository age, disappearing after a
> week or a month.  And the code to generate it can be removed once Fossil
> 2.x is old enough that the chances of running into Fossil 1.x is tiny.
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil 2.1 menu scrunch.

[sky5walk]

Yeah, I'm just pointing out a change from v2.0 and down.
I think it's the 'underlining' effect that is taking extra room as the menu
collapses with zoom. Some earlier versions don't even attempt menu wrap and
make use of horizontal scrollbar. No biggie as I may be confusing stock
skins with whatever fossil-scm.org is adding?

On Wed, Mar 8, 2017 at 6:37 AM, Warren Young  wrote:

> On Mar 7, 2017, at 9:58 AM, sky5w...@gmail.com wrote:
> >
> > But, the scrunch appears with no scrollbar.
>
> I’m not sure what behavior you’re expecting, but what I see looks like
> perfectly sane HTML rendering behavior.  There isn’t enough room for
> “Download”, its padding, or the separator that’s attached to the menu item
> in the CSS.  Therefore, the browser must break the line at that point.
>
> What do you expect instead?
>
> > My zoom is 175%.
>
> If you just want to know how to make that skin work in the window width
> you’re willing to give the browser, despite your zoom level, I see two main
> options:
>
> 1a. Edit the skin to reduce the amount of padding around menu items.
> Under Admin > Skins > CSS, find the “.mainmenu a” block and decrease the
> second “padding” value.  (In 2-value form, the first value is top and
> bottom padding, and the second is left-right padding.)
>
> 1b. Same idea, only reduce font sizes or change typefaces to achieve the
> same end.
>
> 2. Remove menu items you don’t use to make room.  Do this via the same
> path in the UI, except that the last step is Header.
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Fossil 2.1 menu scrunch.

[sky5walk]

I am using Chrome and menu works when extending width of browser.
But, the scrunch appears with no scrollbar. My zoom is 175%.

https://www.reddit.com/r/fossil/comments/5y1ngw/fossil_21f32c36e58a_menu_scrunch_on_chrome/?ref=share_source=link

Thanks for Fossil.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Proposed roadmap for Fossil 2.0

[sky5walk]

Sorry for double post, I got spammed between reply and lost track of what I
deleted. :(

On Wed, Mar 1, 2017 at 11:14 AM,  wrote:

> Cool!
> More 2.0+ requests...
> 1. 'Prune' repo to deliver a branch or whatever as a new repo.
>Ideally, history preserved from point of prune forward.
> 2. Unversioned files supported with check in/out.
>Current approach is confusing(that may be intentional?).
> 3. Fossil 2.0+ delivered as dll.
>I use the exe for remote repo server, but automate my check-in/out's.
>That would be more fluid without parsing CLI text.
>
> Thanks for Fossil(s)!
>
> On Wed, Mar 1, 2017 at 10:56 AM, Richard Hipp  wrote:
>
>> On 2/26/17, Richard Hipp  wrote:
>> > I propose that the next release of Fossil be called "Fossil 2.0"
>>
>> An alpha version of Fossil 2.0 is now live on the main fossil website:
>>
>>  https://www.fossil-scm.org/
>>
>> That same Fossil instance also runs SQLite:  https://www.sqlite.org/src
>>
>> This Fossil 2.0 instance is able to understand SHA3 artifact names,
>> but it does not generate new ones.  So it should interact seamlessly
>> with your current version 1.37 or earlier Fossil client.  And all the
>> web screens should continue to work as they always have.  Please try
>> this out, and if you discover otherwise let me know either on this
>> mailing list or via private email.
>>
>> Thanks for your help.
>> --
>> D. Richard Hipp
>> d...@sqlite.org
>> ___
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Proposed roadmap for Fossil 2.0

[sky5walk]

Cool!
More 2.0+ requests...
1. 'Prune' repo to deliver a branch or whatever as a new repo.
   Ideally, history preserved from point of prune forward.
2. Unversioned files supported with check in/out.
   Current approach is confusing(that may be intentional?).
3. Fossil 2.0+ delivered as dll.
   I use the exe for remote repo server, but automate my check-in/out's.
   That would be more fluid without parsing CLI text.

Thanks for Fossil(s)!

On Wed, Mar 1, 2017 at 10:56 AM, Richard Hipp  wrote:

> On 2/26/17, Richard Hipp  wrote:
> > I propose that the next release of Fossil be called "Fossil 2.0"
>
> An alpha version of Fossil 2.0 is now live on the main fossil website:
>
>  https://www.fossil-scm.org/
>
> That same Fossil instance also runs SQLite:  https://www.sqlite.org/src
>
> This Fossil 2.0 instance is able to understand SHA3 artifact names,
> but it does not generate new ones.  So it should interact seamlessly
> with your current version 1.37 or earlier Fossil client.  And all the
> web screens should continue to work as they always have.  Please try
> this out, and if you discover otherwise let me know either on this
> mailing list or via private email.
>
> Thanks for your help.
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Proposed roadmap for Fossil 2.0

[sky5walk]

All sha's aside:
1. 'Prune' repo to deliver a branch or whatever as a new repo.
   Ideally, history preserved from point of prune forward.
2. Unversioned files supported with check in/out.
   Current approach is confusing(that may be intentional?).
3. Fossil 2.0+ delivered as dll.
   I use the exe for remote repo server, but automate my check-in/out's.
   That would be more fluid without parsing CLI text.

Thanks for Fossil(s)!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Linux binary downloads

[sky5walk]

Thanks, I'll give it a try. :)

On Tue, Feb 21, 2017 at 4:58 AM, Jan Nijtmans 
wrote:

> 2017-02-20 16:42 GMT+01:00 Richard Hipp:
> > On 2/20/17, sky5w...@gmail.com  wrote:
> >> Any chance to get the Windows binary as x64 also?
>
> You can find my win64 build here:
> https://sourceforge.net/projects/cyqlite/files/fossil/
> It is marked 1.37.1, because it is built with openssl 1.1.0e
> and SQLite 3.17.0, and it has a few more fixes discovered
> just after 1.37. (see the 1.37 branch in the fossil repository)
>
> > The problem with that (for me at least) is that it is difficult to
> > compile the OpenSSL library using MSVC.  OpenSSL really wants to be
> > compiled with MinGW.  And I only have a 32-bit MingGW compiler.  So
> > (for me at least) the choices are 32-bit Windows builds, or 64-bit
> > builds that lack "https" capabilities.
>
> So, what's the problem with the mingw-w64 compiler? Works
> fine in my environment, and - as far as I know - in any
> 64-bit windows environment.
>
> Regards,
> Jan Nijtmans
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Linux binary downloads

[sky5walk]

Ah, I see it is somewhat quirky:
https://wiki.openssl.org/index.php/Compilation_and_Installation#W64

Thanks for explaining the Windows x64 gap.

On Mon, Feb 20, 2017 at 10:42 AM, Richard Hipp  wrote:

> On 2/20/17, sky5w...@gmail.com  wrote:
> > Any chance to get the Windows binary as x64 also?
>
> The problem with that (for me at least) is that it is difficult to
> compile the OpenSSL library using MSVC.  OpenSSL really wants to be
> compiled with MinGW.  And I only have a 32-bit MingGW compiler.  So
> (for me at least) the choices are 32-bit Windows builds, or 64-bit
> builds that lack "https" capabilities.
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Linux binary downloads

[sky5walk]

Any chance to get the Windows binary as x64 also?

Thanks for Fossil.

On Mon, Feb 20, 2017 at 9:58 AM, Roy Keene  wrote:

> I'd vote for x86_64 or amd64 (or even EM64T), but not "x64" (which is
> gibberish).
>
> On Mon, 20 Feb 2017, Richard Hipp wrote:
>
> On 2/20/17, Emil Totev  wrote:
>>
>>> Hi
>>>
>>> There are still inconsistencies in the binary downloads for linux at
>>> fossil's web site.
>>>
>>> File fossil-linux-x86-1.37.tar.gz contains a x64 (64-bit) executable.
>>> There seems to be no 32-bit linux executable download.
>>>
>>> Could someone please fix that for this and future builds?
>>>
>>
>> I suspect that the Mac and OpenBSD builds are 64-bits too.  I suppose
>> we could produce 32-bit binaries, but I worry that they would be
>> largely untested, since I use 64-bit machines almost exclusively, as I
>> suspect most of the other Fossil developers do as well.  If you really
>> need a 32-bit binary, you can always build your own use the source
>> tarball, right?
>>
>> Or, perhaps you are simply asking that the downloads be relabeled from
>> "x86" to "x64"?
>>
>> --
>> D. Richard Hipp
>> d...@sqlite.org
>> ___
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] fossil unversioned export * (support globbing)

[sky5walk]

+1...much public outcry...

On Fri, Feb 3, 2017 at 3:52 PM, john lunzer  wrote:

> fossil unversioned is a welcome feature as it allows me to put large
> binary test files in my repo without my .fossil file exploding in size
> every time the test files change.
>
> However, it is currently handicapped by not being able to pull unversioned
> multiple files in a reasonable way.
>
> There was some initial public outcry for this addition but have seen
> nothing recently.
>
> It needs a real pull command. Can I get a +1?
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] unversioned for push/pull users?

[sky5walk]

I do not use sync.
I use automation to pull/push/merge/commit.

I want to use unversioned for dependency files like png,dll,exe,etc.
I prefer the coder to decide unversioned winners and not the file modified
time deciding which is kept.

So, I need some clarification on 'unversioned'?

Push to remote:
  fossil unversioned sync \\someserver\myrepo.fossil
Pull from remote:
  fossil unversioned revert \\someserver\myrepo.fossil

How to checkout unversioned files to local disk?
  fossil unversioned export FILE  //Is this really 1 at a time?!
I could automate this too, but much simpler if a wildcard or 'ALL'?

Thanks for Fossil!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] fast-export to git produces unimportable dump

[sky5walk]

Can confirm with gmail. Every post now has multiple spam replies.
Fossil has been discovered!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Cutting fossil repository

[sky5walk]

Cool.
How does 'fossil purge obliterate' differ from 'fossil shun'?
Is shun obsoleted or superseded by purge now?
Can I achieve the obliteration entirely from the cmd line?

Thanks!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Unversioned files.

[sky5walk]

This is a welcome addition to house nuisance files like bitmaps, icons, etc.
But, I am confused by the in-out nomenclature?

Push to remote: fossil unversioned sync
Pull from remote:   fossil unversioned revert
Checkout unv files: fossil unversioned export FILE  //1 at a time?

If we have the prefix "fossil unversioned", why not allow Push and Pull for
familiarity?
And I'd prefer "fossil checkout" to have an unversioned switch to extract
unv files to disk instead of individual calls/file?

Thanks for Fossil!

On Tue, Aug 30, 2016 at 5:15 PM, Ross Berteig  wrote:

> On 8/30/2016 1:55 PM, Ron W wrote:
>
>> Why only "sync -u" ?
>>
>
> Probably to give an easy way to distinguish developer's clones from full
> mirrors. If the unversioned files are built releases, then I don't need
> them on my dev machine, so no reason to sync them.
>
> If unversioned files are used for something else, syncing them might make
> more sense.
>
> It might also make more sense for that to be controlled by a setting
> rather than a command line option to fossil sync. I'm not sure about that,
> without thinking through other use cases.
>
> On Tue, Aug 30, 2016 at 2:31 PM, Richard Hipp > > wrote:
>>
>> A new feature of Fossil (currently unreleased and only available to
>> people who are willing to recompile the code on trunk) is "unversioned
>> files".
>> 
>>
>
> --
> Ross Berteig   r...@cheshireeng.com
> Cheshire Engineering Corp.   http://www.CheshireEng.com/
> +1 626 303 1602
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil v1.35[3aa86af6aa] - Is this multi-line timeline a bug?

[sky5walk]

Yahoo!
Fossil v1.36[2dec4bdfcb] fixed the problem!
Compiled with VS2013 Express.
Wow, that was weird and confusing. So glad to have unified timeline back.

Thanks for Fossil!

On Wed, Jul 20, 2016 at 10:37 PM,  wrote:

> Curious, I was not familiar with /bloblist URL?
> I found it in the sitemap as 'List Of Artifacts'.
>
> But it does show all 4414 entries with valid events:
> ticket/wiki/filename/commit.
>
> On Wed, Jul 20, 2016 at 10:11 PM, Richard Hipp  wrote:
>
>> On 7/20/16, sky5w...@gmail.com  wrote:
>> > I'll try compiling latest code.
>>
>> Always good to do, even if you are not having problems.  But my guess
>> is that it will make no difference
>>
>> What does the /bloblist URL show you.  Do you have many artifacts.  Do
>> any of them show up as "???"
>>
>> --
>> D. Richard Hipp
>> d...@sqlite.org
>> ___
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil v1.35[3aa86af6aa] - Is this multi-line timeline a bug?

[sky5walk]

Curious, I was not familiar with /bloblist URL?
I found it in the sitemap as 'List Of Artifacts'.

But it does show all 4414 entries with valid events:
ticket/wiki/filename/commit.

On Wed, Jul 20, 2016 at 10:11 PM, Richard Hipp  wrote:

> On 7/20/16, sky5w...@gmail.com  wrote:
> > I'll try compiling latest code.
>
> Always good to do, even if you are not having problems.  But my guess
> is that it will make no difference
>
> What does the /bloblist URL show you.  Do you have many artifacts.  Do
> any of them show up as "???"
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil v1.35[3aa86af6aa] - Is this multi-line timeline a bug?

[sky5walk]

Unfortunately, same results:
c:\myrepo>fossil rebuild myrepo.fossil
  100.0% complete...

c:\myrepo>fossil test-integrity myrepo.fossil
4414 non-phantom blobs (out of 4414 total) checked:  0 errors
low-level database integrity-check: ok

I'll try compiling latest code.

On Wed, Jul 20, 2016 at 9:41 PM, Richard Hipp  wrote:

> Maybe also run "fossil rebuild".  And/or "fossil test-integrity".
> Please report any findings.
>
> On 7/20/16, sky5w...@gmail.com  wrote:
> > ​Thanks for checking. I am confident we have the tip after merging from
> > multiple user commits. But, it is certainly confusing to confirm this
> > visually.
> >
> > http://www.fossil-scm.org/index.html/info/a78e51185326b91f
> > Edited Comment: Partially revert [f73411025e8ebec7]
> > . This
> fixes a
> > problem that when closing a fork by just doing "fossil merge" and
> additonal
> > arrow going up is displayed. Probably not the right fix. Remark:
> reverting
> > more than necessary. Already fixed on trunk.
> >
> > http://www.fossil-scm.org/index.html/info/4cae5c94ea2241b3
> > Comment: (cherry-pick) Fix a timeline bug, showing an unintended arrow
> when
> > closing a fork.
> >
> > Do these commits imply similar errors and fixed on trunk?
> >
> > I will try compiling the latest fossil code and do a rebuild and report
> > back...
> >
> >
> > Thanks for Fossil!
> >
> > On Wed, Jul 20, 2016 at 8:48 PM, Richard Hipp  wrote:
> >
> >> It is difficult to say if this is a bug or a weird repo.  I'd need
> >> access to the repo to tell.
> >>
> >> On 7/20/16, sky5w...@gmail.com  wrote:
> >> > I've noticed weird multi-line timelines with v1.35.
> >> > Is this a bug or is it the skin run amok?
> >> > This repo has only trunk and 1 very old branch.
> >> >
> >> >
> >>
> https://www.reddit.com/r/fossil/comments/4tti7k/fossil_v1353aa86af6aa_is_this_multiline_timeline/
> >> >
> >> > Thanks for Fossil!
> >> >
> >>
> >>
> >> --
> >> D. Richard Hipp
> >> d...@sqlite.org
> >> ___
> >> fossil-users mailing list
> >> fossil-users@lists.fossil-scm.org
> >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> >>
> >
>
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil v1.35[3aa86af6aa] - Is this multi-line timeline a bug?

[sky5walk]

​Thanks for checking. I am confident we have the tip after merging from
multiple user commits. But, it is certainly confusing to confirm this
visually.

http://www.fossil-scm.org/index.html/info/a78e51185326b91f
Edited Comment: Partially revert [f73411025e8ebec7]
. This fixes a
problem that when closing a fork by just doing "fossil merge" and additonal
arrow going up is displayed. Probably not the right fix. Remark: reverting
more than necessary. Already fixed on trunk.

http://www.fossil-scm.org/index.html/info/4cae5c94ea2241b3
Comment: (cherry-pick) Fix a timeline bug, showing an unintended arrow when
closing a fork.

Do these commits imply similar errors and fixed on trunk?

I will try compiling the latest fossil code and do a rebuild and report
back...


Thanks for Fossil!

On Wed, Jul 20, 2016 at 8:48 PM, Richard Hipp  wrote:

> It is difficult to say if this is a bug or a weird repo.  I'd need
> access to the repo to tell.
>
> On 7/20/16, sky5w...@gmail.com  wrote:
> > I've noticed weird multi-line timelines with v1.35.
> > Is this a bug or is it the skin run amok?
> > This repo has only trunk and 1 very old branch.
> >
> >
> https://www.reddit.com/r/fossil/comments/4tti7k/fossil_v1353aa86af6aa_is_this_multiline_timeline/
> >
> > Thanks for Fossil!
> >
>
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Fossil v1.35[3aa86af6aa] - Is this multi-line timeline a bug?

[sky5walk]

I've noticed weird multi-line timelines with v1.35.
Is this a bug or is it the skin run amok?
This repo has only trunk and 1 very old branch.

https://www.reddit.com/r/fossil/comments/4tti7k/fossil_v1353aa86af6aa_is_this_multiline_timeline/

Thanks for Fossil!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Adding a mailing list to Fossil SCM

[sky5walk]

If a built-in forum existed(yay), would users be allowed to upload images
to support their posts/queries/tickets? And if so, could those attachments
be treated less strictly regarding shunning? Deleting occasional
spammer/bot entries will be required.

On Tue, Jun 28, 2016 at 9:40 AM, Warren Young  wrote:

> On Jun 27, 2016, at 9:04 PM, Jonathan Otsuka  wrote:
> >
> > adding a mailing list feature isn’t too far fetched.
> >
> > Has this idea been brought up before?
>
> drh has publicly stated that he would like to write his own email
> server.[1]
>
> However, given Fossil’s nature, I think a web forum might be better.
>
> While I’m generally in favor of mailing lists over web forums, I do think
> that having a web forum system built into Fossil could offer some unique
> advantages over Fossil + a 3rd party web forum which could overcome the
> disadvantages of web forums:
>
> 1. No exposure of email addresses, hence no email spam. :)
>
> 2. Forum spam can’t be forged, violators can be banned, and their unwanted
> posts removed.  (Subject to the same limitations on shunning as we have
> now, of course, so no one could make a “censorship!” cry stick.)
>
> 3. Posts would be Fossil versioned artifacts, with all the benefits that
> derive therefrom.  For just one example, everyone cloning the
> fossil-scm.org repo would also get a copy of the historical Fossil forum
> discussions.  Imagine being able to search the forums for help while
> offline.
>
> 4. Similarly, you could sync your Fossil repos, get on a plane, and answer
> forum posts in the air, then autosync them to the central repo when you get
> back online.
>
> 5. Many of the pieces needed to implement this already exist: tickets are
> nearly forum-like already, we have two perfectly suitable markup language
> processors, we have an RSS generator, we have a perfectly suitable DBMS, an
> FTS engine, etc.
>
> 6. Speaking of FTS, searching the fossil-scm.org forum archive would turn
> up fewer wristwatch and handbag results. :)
>
> 7. If Fossil forum posts worked more like wiki articles than tickets, you
> could edit your posts after posting them, with the history of the post
> available to prevent rewriting history.
>
> 8. Every now and then, someone will pop up on this list asking for some
> kind of email notification.  These people often refuse to be placated by
> the current alternative, RSS.  An automatically-generated sub-forum for
> each of these use cases might do the trick instead.  (Commit messages with
> inline diffs, ticket change notifications, etc.)
>
> 9. The world really needs someone to take a second bite at the apple that
> Discourse tried for.  That *can’t* be the best the open source community
> can come up with.
>
> About the only one of these that you get with a built-in email server +
> mailing list manager in Fossil is that it would be a platform to address
> #8.  My sense is that drh’s wish to implement his own MTA would result in a
> separate piece of software, however, so you wouldn’t even get that benefit,
> except possibly through some kind of email gateway.
>
>
> [1]: https://twit.tv/shows/floss-weekly/episodes/320
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Quotes

[sky5walk]

Fossil is a gem and should not be dismissed or ignored simply because the
masses choose git. In fact, I often find the most elegant solutions in the
extremes.

On Thu, May 19, 2016 at 5:29 PM, Richie Adler  wrote:

> > Not sure it's fair to include my quote when I've never once actually used
> > git, but I appreciate your vote.
>
> You don't need to drill your own head to know that the practice is deadly
> :)
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Why does the repo file grow over time?

[sky5walk]

Nice, I just recovered 50% file size using:
  fossil rebuild --compress-only
I had only ever used fossil rebuild and vacuum's?
Thanks for heads up.

On Fri, Nov 27, 2015 at 5:11 PM, Warren Young  wrote:

> On Nov 27, 2015, at 3:06 PM, Richard Hipp  wrote:
> >
> > On 11/27/15, Warren Young  wrote:
> >> Why is my year-old clone so much larger than a fresh clone?
> >>
> >> And yes, I did re-VACUUM the repo file before posting.  That did shrink
> it
> >> considerably, from about 75 MiB.
> >
> > Did you run "fossil rebuild --compress-only”?
>
> That fixed it.  My year-old clone is now the same size as a fresh one.
>
> So, what did that fix actually do?  What was taking up the extra space,
> which VACUUM did not find?
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Search on file name, display history?

[sky5walk]

Maybe a dumb question, but can search be expanded to repo files? Maybe just
the tip? Is it a speed issue or too many results to process?

On Tue, Nov 10, 2015 at 9:32 PM, jungle Boogie 
wrote:

> Sent from my iPhone 7.1
> On Nov 10, 2015 5:04 PM, "Steve Stefanovich"  wrote:
> >
> > ‎Can the search be extended to search on file names as well, and results
> to include the link to jump straight away to file history?
> >
>
> I support this. Sometimes the file name is known but it's location is
> unknown. Instead of spending time expanding all directories,
>
> > S.
> >
> >
> >
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] source code file is considered by fossil to be binary.

[sky5walk]

Thanks for the fix!
I will try to compile it when I get a spare moment...which is in short
supply.

On Fri, Nov 6, 2015 at 3:16 AM, Jan Nijtmans <jan.nijtm...@gmail.com> wrote:

> 2015-11-06 2:12 GMT+01:00 Richard Hipp:
> > Offending code is here:
> > https://www.fossil-scm.org/fossil/artifact/10cb5eb292?ln=40-43
> >
> > I guess sky5walk wants that to allow through any characters other than
> 0x00
>
> My guess is that the code in doc.c was written when the function
> looks_like_binary() didn't exist yet. Should be fixed now:
>  <https://www.fossil-scm.org/fossil/info/b51ba29365b93b3f>
>
> Whatever definition of BINARY is chosen, I think it should be
> the same everywhere within fossil.
>
> Thanks!
>  Jan Nijtmans
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] source code file is considered by fossil to be binary.

[sky5walk]

Hi,
I am also trapped with this binary file detection for the egregious use of
ascii characters 2 and 6 in my code. :(

;//  ascii2+sometexthere+ascii6
;//sometexthere;<-- pasting here does not show the prefix and suffix
ascii characters.

I cannot see diff's or my source code now in fossil ui.
Note, I do not want to use escape char's.
Is there any chance or setting to let Fossil v134 detection logic use
extended ascii character range?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] source code file is considered by fossil to be binary.

[sky5walk]

No, I just deleted ascii characters 2 and 6 from the file and Fossil now
shows the file as text. I will have to build this ascii string in code
instead of pasting from hex editor. But, it would be cool to set a range of
acceptable ascii characters = text. Ex. ascii 1-127 = text.

On Thu, Nov 5, 2015 at 2:16 PM, Jan Nijtmans  wrote:

> 2015-11-05 19:37 GMT+01:00  :
> > Hi,
> > I am also trapped with this binary file detection for the egregious use
> of
> > ascii characters 2 and 6 in my code. :(
> >
> > ;//  ascii2+sometexthere+ascii6
> > ;//sometexthere ;<-- pasting here does not show the prefix and suffix
> > ascii characters.
>
> As far as I know, fossil doesn't use control characters to decide
> the file is binary, only the null-byte. So I think something else
> is triggering the binary detection. Too long lines, maybe?
>
> Regards,
>Jan Nijtmans
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] source code file is considered by fossil to be binary.

[sky5walk]

No, saving the file to utf-8 + BOM did not prompt Fossil to trigger text.
And "decent" is a relative term.
;// Temp Tol ±°C ;<-- Ansi display :)
;// Temp Tol [xB1][xB0]C ;<-- UTF-8+BOM display :(

On Thu, Nov 5, 2015 at 5:43 PM,  wrote:

> Thanks for looking at this.
> Attached are a small repo(anonymous=setup, password=fossil) and its 2 text
> files.
>
> Thanks for Fossil,
> Steve
>
> On Thu, Nov 5, 2015 at 5:20 PM, Richard Hipp  wrote:
>
>> On 11/5/15, sky5w...@gmail.com  wrote:
>> > Well, I have a workaround(no pasted literal strings). I just didn't
>> realize
>> > Ascii characters within 1-255 could trigger binary?
>> >
>> > Maybe a fast histogram, and a count of << 1 or 2% for these ascii
>> > characters allows text. Or let the user define the valid range.
>>
>> Please send me the actual file that is causing problems.
>>
>> >
>> > By the way, Notepad, Notepad++, Visual Studio, etc. have identical
>> > renderings for these characters and consider the file ansi text.
>> >
>> > On Thu, Nov 5, 2015 at 4:31 PM, Stephan Beal 
>> wrote:
>> >
>> >> On Thu, Nov 5, 2015 at 9:52 PM,  wrote:
>> >>
>> >>> Haha, it would be quite a mess if $ and @ triggered binary.
>> >>> I see no reason to kick the file to binary if the ascii code < 128?
>> >>>
>> >>
>> >> fwiw...
>> >>
>> >> [stephan@host:~/bin]$ hexdump fossil | head
>> >> 000 457f 464c 0102 0001    
>> >> 010 0002 003e 0001  7be2 0040  
>> >> 020 0040    0b38 0094  
>> >> 030   0040 0038 0009 0040 0025 0022
>> >> 040 0006  0005  0040   
>> >> 050 0040 0040   0040 0040  
>> >> 060 01f8    01f8   
>> >> 070 0008    0003  0004 
>> >> 080 0238    0238 0040  
>> >> 090 0238 0040   001c   
>> >>
>> >> (Assumption: that's "probably" typical of a typical binary file.)
>> >>
>> >> i see only 2 bytes there which are >127d (specifically, 0xf8 and 0xe2),
>> >> and lots below 32d. Plus i see a few 6's and 2's. i think it's
>> >> unreasonable
>> >> (=highly unconventional) to expect fossil to treat those bytes as
>> "text."
>> >> 0x02 is, according to my local man pages, the "start of text" (control)
>> >> character, which places it implicitly outside the range of bytes used
>> by
>> >> "text."
>> >>
>> >> --
>> >> - stephan beal
>> >> http://wanderinghorse.net/home/stephan/
>> >> http://gplus.to/sgbeal
>> >> "Freedom is sloppy. But since tyranny's the only guaranteed byproduct
>> of
>> >> those who insist on a perfect world, freedom will have to do." -- Bigby
>> >> Wolf
>> >>
>> >> ___
>> >> fossil-users mailing list
>> >> fossil-users@lists.fossil-scm.org
>> >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>> >>
>> >>
>> >
>>
>>
>> --
>> D. Richard Hipp
>> d...@sqlite.org
>> ___
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] source code file is considered by fossil to be binary.

[sky5walk]

Haha, it would be quite a mess if $ and @ triggered binary.
I see no reason to kick the file to binary if the ascii code < 128?

On Thu, Nov 5, 2015 at 3:46 PM,  wrote:

> No difference besides num bytes with or without the embedded Ascii
> characters 2 and 6.
> I add this 1 line to my file and it triggers binary?!
> [Asc2]+"123 "+[Asc6][CR+LF]
>
> c:\tryfossil>fossil test-looks-like-utf myfile.txt
> File "myfile.txt" has 121343 bytes.
> Starts with UTF-8 BOM: no
> Starts with UTF-16 BOM: no
> Looks like UTF-8: yes
> Has flag LOOK_NUL: no
> Has flag LOOK_CR: yes
> Has flag LOOK_LONE_CR: no
> Has flag LOOK_LF: yes
> Has flag LOOK_LONE_LF: no
> Has flag LOOK_CRLF: yes
> Has flag LOOK_LONG: no
> Has flag LOOK_INVALID: yes
> Has flag LOOK_ODD: no
> Has flag LOOK_SHORT: no
>
> On Thu, Nov 5, 2015 at 3:21 PM, Warren Young  wrote:
>
>> On Nov 5, 2015, at 11:37 AM, sky5w...@gmail.com wrote:
>> >
>> > I am also trapped with this binary file detection for the egregious use
>> of ascii characters 2 and 6 in my code. :(
>>
>> What does “fossil test-looks-like-utf filename” say for that file?
>> ___
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] source code file is considered by fossil to be binary.

[sky5walk]

Yes yes, I am painfully aware of the BOM and the encoding steps.
Notepad++ has a simple menu click for this.
Despite all combinations, Fossil considers the file binary.

On Thu, Nov 5, 2015 at 6:33 PM, Warren Young  wrote:

> On Nov 5, 2015, at 3:54 PM, sky5w...@gmail.com wrote:
> >
> > And "decent" is a relative term.
>
> No, it’s a value judgment.  I judge that a text editor that can’t handle
> UTF-8 is indecent. :)
>
> > ;// Temp Tol ±°C ;<-- Ansi display :)
> > ;// Temp Tol [xB1][xB0]C ;<-- UTF-8+BOM display :(
>
> That isn’t a conversion from ANSI to UTF-8, it’s just sticking a BOM on
> the front of an ANSI file.  The proper encoding of plus-minus + degrees
> would be [C2][B1][C2][B0].  Four bytes, not two.
>
> If you can’t work out how to get your text editor to do this conversion,
> the iconv tool you can install with Cygwin will do it, via the following
> command:
>
>$ iconv -f MS-ANSI -t UTF-8 < original-file > new-file
>
> The new file should be considerably larger than the old, since every
> single-byte ANSI code point over 127 will be encoded by 2-4 bytes in UTF-8.
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] source code file is considered by fossil to be binary.

[sky5walk]

Hi Dr Hipp, I also sent you "try2.fossil" with the offending file inside.
In that repo, I toggled binary-glob settings with no changes to the file
classification as binary.
You are correct, the diff works for the tiny example file, but not if you
try to view the entire file from the ui:
http://localhost:8080/tree?ci=tip

On Thu, Nov 5, 2015 at 6:42 PM, Richard Hipp <d...@sqlite.org> wrote:

> On 11/5/15, sky5w...@gmail.com <sky5w...@gmail.com> wrote:
> > Hi,
> > I am also trapped with this binary file detection for the egregious use
> of
> > ascii characters 2 and 6 in my code. :(
> >
> > ;//  ascii2+sometexthere+ascii6
> > ;//sometexthere ;<-- pasting here does not show the prefix and suffix
> > ascii characters.
> >
> > I cannot see diff's or my source code now in fossil ui.
> > Note, I do not want to use escape char's.
> > Is there any chance or setting to let Fossil v134 detection logic use
> > extended ascii character range?
>
> Background for the list:  sky5walk sent me a sample file that
> contained his two control characters.
>
> What I did:  I checked the sample file into a test Fossil repository.
> I then checked in a change to that file.  "fossil diff" works.
> "fossil diff --tk" works.  "fossil ui" works and shows the diff on the
> webpage.  I have so far been unable to get it to say that the file is
> binary.
>
> Theory: Perhaps sky5walk has a binary-glob setting that indicates that
> the file in his repo is binary?
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] source code file is considered by fossil to be binary.

[sky5walk]

Well, I have a workaround(no pasted literal strings). I just didn't realize
Ascii characters within 1-255 could trigger binary?

Maybe a fast histogram, and a count of << 1 or 2% for these ascii
characters allows text. Or let the user define the valid range.

By the way, Notepad, Notepad++, Visual Studio, etc. have identical
renderings for these characters and consider the file ansi text.

On Thu, Nov 5, 2015 at 4:31 PM, Stephan Beal  wrote:

> On Thu, Nov 5, 2015 at 9:52 PM,  wrote:
>
>> Haha, it would be quite a mess if $ and @ triggered binary.
>> I see no reason to kick the file to binary if the ascii code < 128?
>>
>
> fwiw...
>
> [stephan@host:~/bin]$ hexdump fossil | head
> 000 457f 464c 0102 0001    
> 010 0002 003e 0001  7be2 0040  
> 020 0040    0b38 0094  
> 030   0040 0038 0009 0040 0025 0022
> 040 0006  0005  0040   
> 050 0040 0040   0040 0040  
> 060 01f8    01f8   
> 070 0008    0003  0004 
> 080 0238    0238 0040  
> 090 0238 0040   001c   
>
> (Assumption: that's "probably" typical of a typical binary file.)
>
> i see only 2 bytes there which are >127d (specifically, 0xf8 and 0xe2),
> and lots below 32d. Plus i see a few 6's and 2's. i think it's unreasonable
> (=highly unconventional) to expect fossil to treat those bytes as "text."
> 0x02 is, according to my local man pages, the "start of text" (control)
> character, which places it implicitly outside the range of bytes used by
> "text."
>
> --
> - stephan beal
> http://wanderinghorse.net/home/stephan/
> http://gplus.to/sgbeal
> "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
> those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] source code file is considered by fossil to be binary.

[sky5walk]

No difference besides num bytes with or without the embedded Ascii
characters 2 and 6.
I add this 1 line to my file and it triggers binary?!
[Asc2]+"123"+[Asc6][CR+LF]

c:\tryfossil>fossil test-looks-like-utf myfile.txt
File "myfile.txt" has 121343 bytes.
Starts with UTF-8 BOM: no
Starts with UTF-16 BOM: no
Looks like UTF-8: yes
Has flag LOOK_NUL: no
Has flag LOOK_CR: yes
Has flag LOOK_LONE_CR: no
Has flag LOOK_LF: yes
Has flag LOOK_LONE_LF: no
Has flag LOOK_CRLF: yes
Has flag LOOK_LONG: no
Has flag LOOK_INVALID: yes
Has flag LOOK_ODD: no
Has flag LOOK_SHORT: no

On Thu, Nov 5, 2015 at 3:21 PM, Warren Young  wrote:

> On Nov 5, 2015, at 11:37 AM, sky5w...@gmail.com wrote:
> >
> > I am also trapped with this binary file detection for the egregious use
> of ascii characters 2 and 6 in my code. :(
>
> What does “fossil test-looks-like-utf filename” say for that file?
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] xkcd on git

[sky5walk]

​"​
Even with fossil, I am having trouble justifying why the hassle is worth
the effort.
​"
​
Sorry, but the alternatives
​(I have a Halloween shudder at the thought)​

​are way more effort in the long run.​
I agree, merging is difficult when there are conflicts. But, Fossil and
others show your options to proceed. You are in control.

On Fri, Oct 30, 2015 at 4:08 PM, jungle Boogie 
wrote:

> On 30 October 2015 at 10:56, Scott Doctor  wrote:
> > That is my experience with all VCS systems. Even with fossil, I am having
> > trouble justifying why the hassle is worth the effort.
>
>
> I version control config files for apps, .vimrc files, and small
> scripts just so I can see what changes I make between them and for
> faster setup on new machines. In my very simple setup, I see clear
> benefits of using version control (Fossil and rcs) on these files. I
> can't imagine how serious software dev would work without some form of
> version control.
>
> --
> ---
> inum: 883510009027723
> sip: jungleboo...@sip2sip.info
> xmpp: jungle-boo...@jit.si
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] diff after update

[sky5walk]

Cool, I've often wanted this feature.
fossil diff --whatif

On Fri, Sep 11, 2015 at 10:11 AM, Richard Hipp  wrote:

> On 9/11/15, Stephan Beal  wrote:
> > On Fri, Sep 11, 2015 at 1:22 PM, Richard Hipp  wrote:
> >
> >> I'm not sure "--undo" is the right name for this option.  Other
> >> suggestions?
> >>
> >
> > --from-undo
> > or:
> > --from undo (special-case name)
> >
>
> The code on trunk now does "fossil diff --undo".  I'm very open to
> changes in the name of that option, though.  Maybe "--from-undo" is
> slightly better, but not a great deal.
>
> Adding support for "undo" as a special-case name of "--from" seems
> problematic since that would make it harder to do a diff against a
> branch named "undo".
>
> "fossil diff --versus-undo" maybe???
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Shunning files with confidential information - renames, removed files etc.

[sky5walk]

Nice.
Is it possible to trim the results to only a specific file using a raw SQL
query or TH1?
Or is it quicker to just parse fossil test-whatis-all  artifacts.txt
output?
Can I enter multiple artifacts(comma or space delimited) in the shun ui or
only 1 at a time?

Thanks

On Mon, Aug 17, 2015 at 6:08 PM, Kees Nuyt k.n...@zonnet.nl wrote:


 On Mon, 17 Aug 2015 16:37:41 +0530, Graeme Pietersz
 gra...@pietersz.net wrote:

  I have a Fossil repo that I expected to only work on myself. I have
  files containing confidential information and I now need to allow
  someone else developer access (so clone, push and pull as a minimum) to
  the repo.
 
  I need to do two things:
 
  1) remove past versions of one file that used to contain confidential
  information (it was removed in the latest commit). Does that mean shun,
  rebuild and then add again? How do I ensure all past versions are
  removed? This file has also been renamed so I need to check versions
  using the old path are sunned as well.

 Yes.

  2) ensure that I have never committed another file, and, if I have, shun
  it completely.
  3) shun two files that have been removed, but old versions of which are
  in the repo. They are not hard to find in the UI.
 
  All the files concerned have a  distinctive filename pattern (all start
  the same) and would only ever have been in one of two directories in any
  version. Not sure if that helps.


 I don't have an answer to all of your questions, but I suppose
 the
   fossil test-whatis-all
 command, with some grep or awk magic will help you identify the
 artifacts to shun, and verify the result after the clean-up.

 --
 Regards,

 Kees Nuyt


 I would be very grateful for any help.
 
 Graeme
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Search feature

[sky5walk]

​I read the search feature is in a trial stage.
Can it be expanded to search in actual source files?
Now using the browser and only per file. Or of course in an external tool
in my checkout folder.

Thanks for Fossil.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Ignoring merge conflicts on a binary file

[sky5walk]

The repo still grows and grows with every commit of a binary file. I don't
fully understand this definition?

binary-glob -- The VALUE is a comma or newline-separated list of (versionable)
GLOB patterns that should be treated as binary files for committing and
merging purposes. Example: *.jpg

​Adding *.pdf to the above list means what exactly in terms of repo storage?

On Tue, Jul 28, 2015 at 6:50 PM, Christopher M. Fuhrman cfuhr...@pobox.com
wrote:

 Howdy,

 On Tue, 28 Jul 2015 at 3:43pm, Paolo Bolzoni wrote:

  Dear list,
 
  I am writing a pdf document using LaTeX, since some of the readers
  have problems compiling I'd like to keep also the .pdf under revision
  control.
 
  The .pdf is actually a binary output of other files, so it should be
  ignored during merge conflicts. I know this violated the basics of a
  scm, but it is possible to tell the repository to treat some file
  differently and do not try to merge them, but simply replace?

 I believe doing this:

   $ fossil settings binary-glob *.pdf

 would work.  Probably better to do it from the web ui in case there are
 other values present in that setting.

 Cheers!

 
  Your faithfully,
  Paolo
  ___
  fossil-users mailing list
  fossil-users@lists.fossil-scm.org
  http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
 

 --
 Christopher M. Fuhrman
 cfuhr...@pobox.com


 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Remove redundant shun links from doc page.

[sky5walk]

Ok??? Kinda annoying since I clicked all 4 to see which is more relevant
only to see they are identical. Not sure why this is a preferred output? If
the auto-generate stores to a map with the link as a key, then only 1
identical key will survive. Otherwise, it requires a multi-pass cleanup.

On Mon, Jun 22, 2015 at 1:17 PM, Stephan Beal sgb...@googlemail.com wrote:

 On Mon, Jun 22, 2015 at 7:15 PM, sky5w...@gmail.com wrote:

 This link is referenced 4 times:
 http://www.fossil-scm.org/index.html/doc/trunk/www/shunning.wiki
 Here:
 http://www.fossil-scm.org/index.html/doc/trunk/www/permutedindex.html


 lots of stuff is duplicated on that page - those links are automatically
 generated using various permutations of the link's name. i.e. it's by
 design.


 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal
 Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
 those who insist on a perfect world, freedom will have to do. -- Bigby Wolf

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Remove redundant shun links from doc page.

[sky5walk]

This link is referenced 4 times:
http://www.fossil-scm.org/index.html/doc/trunk/www/shunning.wiki
Here:
http://www.fossil-scm.org/index.html/doc/trunk/www/permutedindex.html

Content From Fossil — Shunning: Deleting
Deleting Content From Fossil — Shunning:
From Fossil — Shunning: Deleting Content
Shunning: Deleting Content From Fossil

My vote is keep only 1:
Shunning - Deleting Content From Fossil

Thanks for Fossil!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Version 1.33 win64

[sky5walk]

In light of the shenanigans at sourceforge, would you consider hosting
elsewhere?

On Fri, Jun 12, 2015 at 8:09 AM, Jan Nijtmans jan.nijtm...@gmail.com
wrote:

 2015-05-25 11:34 GMT+02:00 Jan Nijtmans:
  For anyone interested, I built fossil 1.33 especially
  for win64, it's available here:
 
  https://sourceforge.net/projects/cyqlite/files/fossil/
 
  This binary is compiled with latest MinGW-w64 compiler,
  and with json support, ssl support, tcl support, th1-docs
  and th1-hooks support and with legacy-mv-rm support.
  (If you don't know what this all means, you
  probably don't need it but it won't hurt either)

 Minor update. Since openssl 1.0.2b is just released with
 a few security fixes, and a fix for the crash in the /reports
 web-page was developed
  http://fossil-scm.org/index.html/info/8184f39d803f9ad6
 I just rebuilt the win64 fossil binary with those 2 changes.
 It can be downloaded from the same place:
 https://sourceforge.net/projects/cyqlite/files/fossil/

 Regards,
   Jan Nijtmans
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] WARNING: multiple open leaf check-ins on trunk:

[sky5walk]

Thanks for explaining this new feature. v1.33 showed a months old forgotten
commit and it was easy to merge and clean up. Wasn't sure how merging such
old changes would go.

Thanks for Fossil!

On Fri, May 29, 2015 at 10:24 PM, Doug Franklin nutdriverle...@comcast.net
wrote:

 On 2015-05-29 19:19, Ron W wrote:

  I suspect, in most case, multiple independent branches with the same
 name are not a problem. But trunk is a special case that may warrant a
 warning.


 I don't think I'd take that suspicion to the bank.  Personally, I think it
 should warn on duplication of an existing tag or branch name, with a
 --force option if you know what you're doing. :)  [Grin because I hose
 myself most often when I'm sure I'm doing the right thing.]

 --
 Thanks,
 DougF (KG4LMZ)

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] workflow question

[sky5walk]

Yes, I asked about this in another thread. Can we use TH1 to color the
Timeline entries per User?

On Wed, May 27, 2015 at 1:30 PM, Ron W ronw.m...@gmail.com wrote:

 On Wed, May 27, 2015 at 7:25 AM, Richard Hipp d...@sqlite.org wrote:

 Fossil provides capabilities that make
 it trival for the instructor to see that a student has pushed to
 trunk


 It would be even more trivial to see such pushes if fossil time line could
 color the user names in the timeline display. Even more helpful would be if
 the branch took its color from the user that created it. Then in the
 timeline, if the user color was not the same as the branch color, it would
 stand out rather prominently.


 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Change Branche color

[sky5walk]

How can I dynamically set the commit color by user using th1 in the CSS?

Thanks for fossil.

On Sat, May 9, 2015 at 10:22 AM, Kai Lauterbach kla...@web.de wrote:

 Hi,

 i tried to set the color of a branch as it is described here:
 http://fossil-scm.org/xfer/help/commit

 But it does not work for me, it dies not change the color in the
 Webinterface. But change of the color for one commit is possible.

 I know that the use of the --branchcolor is not recommended but I don't
 like the color which is chosen by fossil. It has chosen brown... On the
 web It looks like that there is something wrong
 with the branch.

 Maybe someone could help me?

 Thanks!!

 kai
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil security question from a newbie

[sky5walk]

The repo is an open SQLite db. You can browse it easily with any 3rd party
​SQLite viewer/editor or your own code. The passwords are hashed but
available. As are the user settings. So, someone could edit the user guest
cap to 'as' and do whatever. Better to encrypt the repo when in transit.

On Tue, Mar 17, 2015 at 11:44 PM, Byung-Jae Kwak byung.k...@gmail.com
wrote:

 Hello,

 Suppose I have .fossil file on a thumb drive and I lost it.
 If all the privileges of all the accounts in the repository have
 been disabled except for the admin account, and the admin
 account is protected with a fairly strong password,
 can I assume the content in the repository is reasonably
 safe?

 BJ
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] How to change background color dynamically?

[sky5walk]

Thanks!
That worked but why not with other globals? Are they not available with the
default fossil.exe?

I initially tried this TH1 in the CSS but it failed and assumed it was not
allowed?
/* This fails */
th1
  if { [ string last c $project_name ] == [ string length $project_name ]
- 1 } {
puts background: lightyellow;
  } else {
puts background: mistyrose;
  }
/th1

/* This works but not my intended logic */
th1
  if { [ string last c $baseurl ] == [ string length $baseurl ] - 1 } {
puts background: lightyellow;
  } else {
puts background: mistyrose;
  }
/th1

Please add a mention of TH1 allowed in CSS.

http://fossil.include-once.org/fossil-skins/wiki?name=TH1
  It can be used in the header, footer, or CSS within th1.../th1
sections, or in the th1-setup settings textbox.

Thanks for Fossil!

On Sun, Mar 15, 2015 at 4:57 AM, mario ma...@include-once.org wrote:

 Sat, 14 Mar 2015 20:06:06 -0400 sky5w...@gmail.com:

  ...
  clones. I understand TH1 only works inside the header/footer
  sections, so is it possible to maybe change just their backgrounds?
  Currently, CSS sets my entire background color.

 You can also use TH1 for the stylesheet (Admin  CSS). It's a proper
 template just like header and footer.

 Basically you'd just add something like:

th1
if [regexp localhost $baseurl] {
  puts body { background: red; }
}
/th1

 Alternatively try Admin  Logo to set a background image.
 Your local instance can have a configuration different to your
 online version. (Doesn't change until you `fossil config push..`)
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] How to change background color dynamically?

[sky5walk]

Hi,
All the skinning going on recently got me interested in tweaking my repo
appearance. Not being html/css savvy in the least, I am stumped how to
trick the CSS to use a variable background color if remote or localhost? Or
I could key on the repo name if I append a 'c' to my clones.
I understand TH1 only works inside the header/footer sections, so is it
possible to maybe change just their backgrounds? Currently, CSS sets my
entire background color.

Thanks for Fossil!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] directory structure

[sky5walk]

Richard Hipp wrote I keep most of my Fossil repos in a common directory:
~/www/repos.  I currently have 64 of them sitting there.

What are you holding out on us?!
1. sqlite
2. sqlite - super awesome next
3. fossil
4. tcl editor - nsa proof
5. hal 2.0 - AI that scares Gates, Hawking and Musk
6. .. 64. ??

On Tue, Feb 10, 2015 at 7:05 PM, Barry Arthur barry.art...@gmail.com
wrote:

 I keep all my fossils in /mnt/museum/ and then I clone each fossil to
 the place it is needed, with a working directory below it. The
 /mnt/museum directory is on a separate disk to my working disk, so
 with auto-sync I get free backups. Having all fossils in one directory
 makes for easier off-box backups too.

 So, more graphically, that is:

 /mnt/museum/
   something.fossil
   documents.fossil


 /home/user/projects/something.fossil   (as a clone)
 /home/user/projects/something/ (working dir)

 /home/user/documents.fossil(clone)
 /home/user/documents/  (working)

 The `fossil all ls | grep -v museum` command shows me where all my
 clones are.


 On 11 February 2015 at 05:03, Ron W ronw.m...@gmail.com wrote:

 On Tue, Feb 10, 2015 at 12:24 PM, Jeff Rogers dv...@diphi.com wrote:

 So what I'm thinking about is instead:
 $ cd ~/dev/
 $ fossil clone http://whatever/projectname ~/fossil_repos/projectname.
 fossil
 $ mkdir projectname
 $ cd projectname
 $ fossil open ~/fossil_repos/projectname.fossil


 I use a variant of that:

 ~/Projects
   /repos
 /foo.fossil
 /bar.fossil
   /foo
   /bar


 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users



 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] FLOSS interview

[sky5walk]

Yes, always interesting to hear from Dr Hipp.
1. I had not considered fossil all push/pull.
2. I was hoping for a followup question to:
   Fossil does not perform well with very large repo's or histories  15
years.
   How is the performance hit quantified? 1day or 1hour / 1GB repo / commit?
   What is the limiting factor?
   Is it SQLite or the fossil approach itself?
   Is there a path to improve this performance similar to the SQLite speed
gains in the last 2 years?

Thanks for Fossil!

On Thu, Jan 8, 2015 at 1:05 PM, Stephan Beal sgb...@googlemail.com wrote:

 On Thu, Jan 8, 2015 at 6:34 PM, bch brad.har...@gmail.com wrote:

 Time to collect information on the weak/missing parts and either add
 them to the comments of FLOSS Weekly, get Leo to publish an addendum
 note, or publish an addendum on fossil-scm.org w/ link to original
 interview.


 @Richard:

 https://www.fossil-scm.org/fossil/eventedit

 ;)

 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal
 Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
 those who insist on a perfect world, freedom will have to do. -- Bigby Wolf

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] auto-sync before merge?

[sky5walk]

​My early experience with Fossil and autosync ON was not intuitive and I
may have experienced Dr Hipp's scenario. In my case, slow remote repo's. I
decided ​on a granular approach automated by my own code.

autosync OFF
Start{
fossil status ...
...review uncommitted local changes and fossil commit
fossil pull ...
fossil update ...
fossil leave ...
...review any leaves and fossil merge
fossil commit ...
fossil push ...
Stop}

Can someone explain their autosync ON flow and why adding more auto to it
would be considered contradictory?
Start{
fossil status ...
...review uncommitted local changes and fossil commit
//is this handled by autosync? fossil pull ...
//is this handled by autosync? fossil update ...
//is this handled by autosync? fossil leave ...
//is this handled by autosync? ...review any leaves and fossil merge
fossil commit ...
fossil push ...
Stop}

On Fri, Oct 10, 2014 at 10:45 AM, Andy Bradford amb-fos...@bradfords.org
wrote:

 Thus said =?UTF-8?Q?Ramon_Rib=C3=B3?= on Fri, 10 Oct 2014 10:01:47 +0200:

  If autosync is activated, of course it should do it. In fact, I see it
  as an error not doing it. Does not 'autosync' means: do all the pushes
  and pulls necessary  to keep local repository  always syncronized with
  remote repository?

 I  believe the  original intent  for autosync  was as  a fork  avoidance
 mechanism. Merge does not fork.

 I for one don't think it necessary  to have autosync with merge, but can
 see why some would want it---hopefully  as an option that is disabled by
 default.

 Andy
 --
 TAI64 timestamp: 40005437f12f


 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] More on Fossil-v-Git

[sky5walk]

Repo backups saved me in this scenario. A developer did a fossil add *.* by
mistake and committed. Well, that bloated our repo size tenfold. We knew
quickly because push/pulls were taking too long. A query to this mailing
list mentioned shun's and rebuilds, but I had already made some poor hacks
to remove the offending files. I was trying to eliminate ~300 so manual
shunning was out of the question.
Fastforward - I went to a backup repo immediately prior to the offensive
commit and started over. We regained our repo size and learned our lesson.
In fact, it begs the question; Can I block any command that includes *.*?
I asked about an automated shun, but shun is not available except through
ui. :(


On Fri, Sep 5, 2014 at 3:52 PM, Warren Young war...@etr-usa.com wrote:

 On 9/5/2014 13:36, Matt Welland wrote:

 On Fri, Sep 5, 2014 at 12:10 PM, Ron W ronw.m...@gmail.com
 mailto:ronw.m...@gmail.com wrote:

 Still need to keep the Fossil repo backed up.

 Is there really a need for a backup if you have offsite fossils to which
 you regularly sync?


 Probably not.

 I do it anyway because I'm pretty irregular in how often I sync each
 offsite clone to the master.  It makes me feel better to have a cron job to
 backstop me.

 This also allows me to do a few things differently than a simple fossil
 clone sync:

 1. sqlite3 $repo .dump | xz  $repo.sql.xz gives a somewhat smaller file
 than the binary repo, and it is theoretically readable if you have to do
 some deep disaster recovery.

 2. You can follow that with a GPG pass to encrypt it for semi-secure
 offsite storage, such as Dropbox or Google Drive.  Running whole-archive
 XZ-compressed data through GPG gives an attacker less of a foothold than
 the individually-compressed blobs in the binary Fossil repo.
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] More on Fossil-v-Git

[sky5walk]

Interesting, but I am unsuccessful attempting to read any of what you post?
Can you provide a url directly to 'fx shun add' documentation?
Or do I have to install this to become Armed  Dangerous? :)


On Fri, Sep 5, 2014 at 4:39 PM, Andreas Kupries andre...@activestate.com
wrote:

 On Fri, Sep 5, 2014 at 1:24 PM,  sky5w...@gmail.com wrote:
  I asked about an automated shun, but shun is not available except through
  ui. :(

 http://core.tcl.tk/akupries/fx/index

 fx help ...

 Advanced
 Armed  Dangerous
 Shunning
 fx shun add uuid...   Shun artifacts
 fx shun listShow the list of all shunned
 artifacts
 fx shun remove uuid...Reaccept artifacts which have
 been shunned
 fx shunned  Show the list of all shunned
 artifacts

 --
 Andreas Kupries
 Senior Tcl Developer
 Code to Cloud: Smarter, Safer, Faster™
 F: 778.786.1133
 andre...@activestate.com, http://www.activestate.com
 Learn about Stackato for Private PaaS: http://www.activestate.com/stackato

 21'st Tcl/Tk Conference: Nov 10-14, Portland, OR, USA --
 http://www.tcl.tk/community/tcl2014/
 Send mail to tclconfere...@googlegroups.com, by Sep 8
 Registration is open.
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Off-topic faith declarations (was Re: how to use git to lose data)

[sky5walk]

Well said and yes, Fossil is a non-tedious, benevolent lifesaver. My
reservation being scalability of large repo support. While I am unaffected,
those professionals charged with release and maintenance of large code
bases look past Fossil and its SQLite core.
Questions:
Will Fossil ever seek to address very large source control?
Can Fossil offer 2 solutions? SQLite based and PostgreSQL(insert big RDB
here)?

Thanks for Fossil!


On Tue, Sep 2, 2014 at 9:31 AM, Richard Hipp d...@sqlite.org wrote:




 On Tue, Sep 2, 2014 at 8:57 AM, Marcelo richiead...@gmail.com wrote:

 2014-09-02 5:44 GMT-03:00 Gour g...@atmarama.net:

  10) Considering 9) (above) it's a proof that those serving God, serve
  other people as well.


 As a atheist I protest that this is deeply unsettling and off-topic.


 I think that Gour's comment was appropriate to the subject at hand and in
 good taste. Gour's remark was in no way judgmental or condescending and it
 contributed (tangentially) to the topic. Marcelo's reply, on the other
 hand, loudly proclaims his particular world-view and posits that anyone who
 disagrees must remain silent.  Marcelo's reply is definitely off-topic.

 Marcelo, you are welcomed to contribute and ask questions and comment here
 and I hope that you will continue to participate in this forum.  However, I
 ask that in the future you keep your remarks civil and on-topic and that
 you avoid trying to enforce your world-view on other members of the
 community.
 --
 D. Richard Hipp
 d...@sqlite.org

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Scalability (WAS: something else)

[sky5walk]

While disabling checksums helps with speed
http://www.fossil-scm.org/index.html/help?cmd=settings
It does not help with redundant binary images in the repo.
For that, you have to shun and rebuild.
If you could flag a file as Keep latest only, that would be less
painless. I don't mind the artifact overhead of a changed binary file, but
it hurts to have the data stored too.


On Tue, Sep 2, 2014 at 4:47 PM, Joerg Sonnenberger jo...@britannica.bec.de
wrote:

 On Tue, Sep 02, 2014 at 02:45:13PM -0600, Warren Young wrote:
  Fossil currently wants to do a cryptographically strong checksum on
  every version of every graphic file I've ever created on every
  checkin.  Consequently, a checkin takes several seconds here.
 
  There was a recent proposal that you should be able to turn that
  feature of Fossil off, which would help a lot in such cases.

 Huh? You can. It has been available for ages.

 Joerg
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Scalability (WAS: something else)

[sky5walk]

​
(2) Fossil's purpose is to be able to recreate historical versions of the
project - exactly.  It cannot do that if historical images have been
deleted.
I understand the purity intended, but continue to be frustrated by it. :) I
merely seek an automated way within Fossil to manage garbage. Re-repoing to
delete spam or 'add *.*' mistakes is quite painful.


On Tue, Sep 2, 2014 at 5:19 PM, Warren Young war...@etr-usa.com wrote:

 On 9/2/2014 15:07, sky5w...@gmail.com wrote:

 If you could flag a file as Keep latest only, that would be less
 painless.


 That wouldn't work for me.  I want the past versions of the image. [*]

 The branch I made of the web app three years ago won't run right with the
 current bitmaps.  The new ones may be different sizes, have a different
 design esthetic, etc.

 With repo-cksum on, Fossil has an O(N) complexity component.  Without it,
 you only have the logarithmic time complexities due to the tree structures
 of the DB.


 [*] Well, I suppose I could go through and weed out a few bad ideas, but
 that goes against Fossil's nature.

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Version 1.28 release?

[sky5walk]

Took time to reply, cause I had to clean the coffee I spit up!
A released application should be considered stable and a conservative view
would say its libs should not contain alphas or betas.
The ease of compiling a bleeding edge Fossil.exe is already in place for
those wishing to gain the latest features in trunk.

Fossil is a critical application that deserves its own shelf.

Thanks for Fossil and SQLite!


On Thu, Jan 9, 2014 at 10:21 AM, Remigiusz Modrzejewski
l...@maxnet.org.plwrote:


 On Jan 9, 2014, at 16:14 , Richard Hipp wrote:

  On Thu, Jan 9, 2014 at 10:12 AM, Remigiusz Modrzejewski
  l...@maxnet.org.plwrote:
  I second this view, Fossil is definitely valuable on its own merit.
  As such, its stable versions should not contain alpha-quality code from
  other projects.
 
 
  SQLite alphas are more robust that stables of most other software
  projects.

 Good point.
 However, this is one that can be hard to explain to distributors.
 It would be a shame to see new Fossil releases not adopted due to that.
 Disclaimer: I have no idea if this would be the case.
 Personally, knowing SQLite testing, I have nothing against using current
 version in my system.

 Kind regards,
 Remigiusz Modrzejewski



 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Version 1.28 release?

[sky5walk]

A while back when considering Fossil, I read that 'any' database could have
been chosen in its design. This thread seems to contradict Fossil's
published design theme?

http://www.fossil-scm.org/fossil/doc/tip/www/theory1.wiki
Thoughts On The Design Of The Fossil DVCS:
We claim that Fossil is not based on SQLite at all and that Fossil is not
based on a distributed NoSQL database because Fossil is a distributed NoSQL
database.

Fossil Is A NoSQL Database
We begin with the first question: Fossil is not based on a distributed
NoSQL database because Fossil *is* a distributed NoSQL database. Fossil is
*not* based on SQLite. The current implementation of Fossil uses SQLite as
a local store for the content of the distributed database and as a cache
for meta-information about the distributed database that is precomputed for
quick and easy presentation. But the use of SQLite in this role is an
implementation detail and is not fundamental to the design. Some future
version of Fossil might do away with SQLite and substitute a pile-of-files
or a key/value database in place of SQLite. (Actually, that is very
unlikely to happen since SQLite works amazingly well in its current role,
but the point is that omitting SQLite from Fossil is a theoretical
possibility.)

I treat Fossil as a standalone and critical app and believe it deserves
higher standing than a test bed for SQLite.

Thanks for Fossil and SQLite!


On Thu, Jan 9, 2014 at 11:52 AM, Remigiusz Modrzejewski
l...@maxnet.org.plwrote:


 On Jan 9, 2014, at 16:35 , sky5w...@gmail.com wrote:

  Took time to reply, cause I had to clean the coffee I spit up!
  A released application should be considered stable and a conservative
 view
  would say its libs should not contain alphas or betas.
  The ease of compiling a bleeding edge Fossil.exe is already in place for
  those wishing to gain the latest features in trunk.

 You do realize that alpha and beta are just words?
 With different quality assurance procedures in different projects,
 trying to use them as a gauge of anything else than releaser intent is
 misleading.
 SQLite QA is so impressive that some may be pretty comfortable with having
 any version,
 provided it has passed a full test suite, included in their systems.

 The problem here is the message sent by the word alpha.
 What it usually means is I just wrote it, hope it will not explode in
 your face, but no warranties.
 Therefore if we want to say Fossil is rock-solid, we can't say it uses
 alpha libs,
 just to avoid the confusion, no matter the actual quality.


 Kind regards,
 Remigiusz Modrzejewski



 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Question on repo size after repeated binary file commits?

[sky5walk]

I am curious what is stored in the repo for each new commit that includes a
tiny change to a binary file.
Whether a dll or an image file, is fossil storing each binary file
compressed, uncompressed or some sort of delta?
Over time(6mo's to 1yr), I would like to reduce my repo size by purging
really old binary files.

Thanks for fossil!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Question on repo size after repeated binary file commits?

[sky5walk]

Ah, is there a way to quantify the binary delta?
If I have a 1MB binary file and commit a 1 byte change, what is the size of
the computed binary delta?

You are correct of course, but I tend not to extend the spirit of fossil to
binary files and images. It is their existence and not legacy that is
critical in my application.

An example would be icons used for toolbars and menus. If I tweak them or
add layering, I sorta obsolete the originals. Here, I prefer the smaller
repo.


On Sun, Dec 22, 2013 at 1:46 PM, Mark Janssen mpc.jans...@gmail.com wrote:



 On Sun, Dec 22, 2013 at 7:37 PM, sky5w...@gmail.com wrote:

 I am curious what is stored in the repo for each new commit that includes
 a tiny change to a binary file.
  Whether a dll or an image file, is fossil storing each binary file
 compressed, uncompressed or some sort of delta?
 Over time(6mo's to 1yr), I would like to reduce my repo size by purging
 really old binary files.

 Thanks for fossil!


 Fossil does have delta encoding but I am not sure whether this is  used
 for binary files. However part of the design philosophy of Fossil is that
 no history is ever lost. So reducing the repository size is generally not
 possible.

 Mark

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Question on repo size after repeated binary file commits?

[sky5walk]

Thanks. I didn't know how binary was handled given the Timeline diff
response = cannot compute difference between binary files.
I think it would be cool if instead fossil listed some of the metrics used
or determined in the binary delta operation.

Thanks for Fossil!


On Sun, Dec 22, 2013 at 2:51 PM, Stephan Beal sgb...@googlemail.com wrote:

 On Sun, Dec 22, 2013 at 8:44 PM, sky5w...@gmail.com wrote:

 Ah, is there a way to quantify the binary delta?
 If I have a 1MB binary file and commit a 1 byte change, what is the size
 of the computed binary delta?


 Very, very small:

 Create two binaries with a one-byte difference:

 [stephan@host:~/cvs/fossil/libfossil]$ cat f-tag  foo; echo -n x  foo;
 cat f-wiki  foo

 [stephan@host:~/cvs/fossil/libfossil]$ cat f-tag  bar; echo -n y  bar;
 cat f-wiki  bar


 [stephan@host:~/cvs/fossil/libfossil]$ l foo bar
 -rw-rw-r-- 1 stephan users 1281922 Dec 22 20:48 bar
 -rw-rw-r-- 1 stephan users 1281922 Dec 22 20:48 foo

 The delta:

 [stephan@host:~/cvs/fossil/libfossil]$ ./f-delta foo bar
 4tz2
 2Qjj@0,1:yO@0,2UEw@2Qk7,3wep03;

 Confirm that the delta actually does what's expected:

 [stephan@host:~/cvs/fossil/libfossil]$ ./f-delta foo bar  baz
 [stephan@host:~/cvs/fossil/libfossil]$ ./f-delta -a baz foo  bar2
 [stephan@host:~/cvs/fossil/libfossil]$ cmp bar bar2
 [stephan@host:~/cvs/fossil/libfossil]$ echo $?
 0

 To answer your question: 37 bytes:

 [stephan@host:~/cvs/fossil/libfossil]$ l baz
 -rw-rw-r-- 1 stephan users 37 Dec 22 20:49 baz

 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal
 Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
 those who insist on a perfect world, freedom will have to do. -- Bigby Wolf

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Question on repo size after repeated binary file commits?

[sky5walk]

Really, I am only implying some minimal file statistic like 'DeltaSize(%)'
or somesuch to show the user it is in fact compared internally. The current
message contradicts what is in fact happening. Maybe change that message to
Cannot visually display binary diffs. DeltaSize(%) = -10.


On Sun, Dec 22, 2013 at 3:15 PM, Stephan Beal sgb...@googlemail.com wrote:

 On Sun, Dec 22, 2013 at 9:06 PM, sky5w...@gmail.com wrote:

 Thanks. I didn't know how binary was handled given the Timeline diff
 response = cannot compute difference between binary files.


 That message is a bit misleading. It really means a visual difference.
 There isn't a mechanism to show a textual diff for binaries, and fossil's
 internal deltas and its text diffs are two completely different beasts.


 I think it would be cool if instead fossil listed some of the metrics
 used or determined in the binary delta operation.


 The diff-related pages don't actually use the delta code (though
 diff/delta are logically similar, they are much different implementations).
 A delta blob does in fact know (without expensive processing) the size of
 the original blob and the size of the delta, so it might be feasible to do
 that. The unsightly part is that fossil doesn't really know what's a binary
 and what isn't (the delta algorithm is the same for all data). When
 performing a textual diff and it runs into any binary-looking data, it
 aborts the diff and assumes that it's binary. i.e. it would first need to
 run through the text diff and, as a fallback, generate statistics for a
 binary delta. Yeah, doable, but IMO horribly ugly because it would have to
 be done as a fallback for the diff generation, making it more expensive
 (computation/memory) than it really needs to be.

 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal
 Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
 those who insist on a perfect world, freedom will have to do. -- Bigby Wolf

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users