Re: [fossil-users] Timeline graph display options

2015-03-09 Thread Richard Hipp
On 3/9/15, Andy Bradford wrote: > Perhaps if there were > 15--20 rails, where they were taking up a disproportionate amount of > space (2) might make a big enough difference. > Oh, it does. Try a graph with "n=all" and you'll see. When you start to get a lot of rails, and the graph gets a

Re: [fossil-users] Timeline graph display options

2015-03-09 Thread Andy Bradford
Thus said Richard Hipp on Mon, 09 Mar 2015 23:06:59 -0400: > Which timeline graph do you prefer: > > (1) https://www.fossil-scm.org/fossil/timeline?y=ci&nomo=0 > (2) https://www.fossil-scm.org/fossil/timeline?y=ci&nomo=1 (1) because the relationship to the node from which the arrow originates is

Re: [fossil-users] Fossil 1.31 directory name

2015-03-09 Thread Joe Prostko
On Sat, Mar 7, 2015 at 6:51 PM, Andy Goth wrote: > Fossil 1.31 has been published to the SlackBuild website. > > http://slackbuilds.org/repository/14.1/development/fossil/ Very cool. I still didn't get around to making the Haiku packages yet, even though the build recipe has existed since the d

Re: [fossil-users] Timeline graph display options

2015-03-09 Thread Joe Prostko
On Mon, Mar 9, 2015 at 11:06 PM, Richard Hipp wrote: > > Which timeline graph do you prefer: > > (1) https://www.fossil-scm.org/fossil/timeline?y=ci&nomo=0 > (2) https://www.fossil-scm.org/fossil/timeline?y=ci&nomo=1 I personally prefer 2. Initially 1 looks more aesthetically pleasing, but when

[fossil-users] Timeline graph display options

2015-03-09 Thread Richard Hipp
Which timeline graph do you prefer: (1) https://www.fossil-scm.org/fossil/timeline?y=ci&nomo=0 (2) https://www.fossil-scm.org/fossil/timeline?y=ci&nomo=1 The difference is in the merge lines. Other examples: (1) https://core.tcl.tk/tk/timeline?y=ci&nomo=0 (2) https://core.tcl.tk/tk/timeline?y=c

Re: [fossil-users] Justification for two-step mv and rm

2015-03-09 Thread Tontyna
Am 09.03.2015 um 10:09 schrieb Jan Nijtmans: Done now: This means that whatever happens with "fossil rm|mv|delete", the "fossil rename" and "fossil forget" will continue to function as they do now. Hurray and thank you! Will

Re: [fossil-users] Working with Windows mapped network drives

2015-03-09 Thread Tontyna
This has nothing to do with mapped drives. You'll get "not found" with any drive root -- C:\, D:\... Fossil cuts off the trailing backslash with the result that stat() resp lstat() returns an error => "not found". I'm not shure whether and if yes in which function(s) -- file_canonical_name()

Re: [fossil-users] Timeline pointers patch

2015-03-09 Thread Richard Hipp
On 3/9/15, Chad Clabaugh wrote: > Ah, no, not yet. Is this something I can fax or must it be mailed? > For this, an emailed scan will be sufficient. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org htt

Re: [fossil-users] Timeline pointers patch

2015-03-09 Thread Chad Clabaugh
Ah, no, not yet. Is this something I can fax or must it be mailed? On Mon, Mar 9, 2015 at 11:32 AM, Richard Hipp wrote: > On 3/9/15, Chad Clabaugh wrote: > > I see what you mean. Modified and tested in Firefox, Chrome, IE. > > > > Brilliant. Thanks. The arrows look *really good* on a 300DPI t

Re: [fossil-users] Timeline pointers patch

2015-03-09 Thread Richard Hipp
On 3/9/15, Chad Clabaugh wrote: > I see what you mean. Modified and tested in Firefox, Chrome, IE. > Brilliant. Thanks. The arrows look *really good* on a 300DPI tablet now! Do I already have a Contributor's Agreement on file from you? (https://www.fossil-scm.org/fossil/doc/trunk/www/copyright

Re: [fossil-users] Timeline pointers patch

2015-03-09 Thread Chad Clabaugh
I see what you mean. Modified and tested in Firefox, Chrome, IE. On Fri, Mar 6, 2015 at 10:14 PM, Richard Hipp wrote: > On 3/6/15, Richard Hipp wrote: > > On 3/6/15, Chad Clabaugh wrote: > >> I would like to offer the attached patch to timeline.c that smooths the > >> timeline arrows while als

Re: [fossil-users] need additional padding for the .filelist li

2015-03-09 Thread Svyatoslav Mishyn
(Mon, 09 Mar 06:15) Richard Hipp: > On 3/8/15, Svyatoslav Mishyn wrote: > > Hello, > > > > for example: > > padding: 1px 0; > > > > see: > > https://cloud.openmailbox.org/public.php?service=files&t=27ee378f8bdc47ebcd06069d907916fc > > What is that hyperlink suppose to demonstrate? I do not under

Re: [fossil-users] need additional padding for the .filelist li

2015-03-09 Thread Richard Hipp
On 3/8/15, Svyatoslav Mishyn wrote: > Hello, > > for example: > padding: 1px 0; > > see: > https://cloud.openmailbox.org/public.php?service=files&t=27ee378f8bdc47ebcd06069d907916fc What is that hyperlink suppose to demonstrate? I do not understand why extra padding is needed. > > > -- > http://

Re: [fossil-users] Justification for two-step mv and rm

2015-03-09 Thread Jan Nijtmans
2015-03-06 16:58 GMT+01:00 Jan Danielsson : > On 06/03/15 15:10, Jan Nijtmans wrote: >> Any objections against adding "fossil forget" as alias >> to "fossil rm" If not, I'll be glad to add it, awaiting >> further discussion. > >No objection. I'm even going to go so far as to say I'll be c

Re: [fossil-users] Commit without resolving the new files: a bug or a feature?

2015-03-09 Thread Stephan Beal
On Mon, Mar 9, 2015 at 9:29 AM, Henry Adi Sumarto < henry.adisuma...@gmail.com> wrote: > (either by adding or by ignoring the file). Shouldn't fossil warn me about > the "extra" files? Or is it intended to work that way? > The behaviour you are seeing is as expected. Fossil requires that you tell

[fossil-users] Commit without resolving the new files: a bug or a feature?

2015-03-09 Thread Henry Adi Sumarto
Hi, When there is a file change in an existing repository and there is another new file that has not been added into the repository, and then I commit the change without adding the new file (let's say I forget to add!), I notice that fossil lets me commit without resolving what to do with the new