Re: [fossil-users] (no subject)
On 27 February 2015 at 21:17, jungle Boogie jungleboog...@gmail.com wrote: Attached is a list of all, what I believe are comments, from src/*.c that contain checkin. I'm assuming these are diffs against trunk tip of the time of writing, but perhaps next time it's useful to mention the checkin/check-in version against which the diff was made. Michai ___ 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] (no subject)
On 27 February 2015 at 21:17, jungle Boogie jungleboog...@gmail.com wrote: Attached is a list of all, what I believe are comments, from src/*.c that contain checkin. I'll pick this one up. Did you mean to change the actual option-names too? Help will be regenerated after a recompile, after a change in corresponding comment-sections in source-files. Michai ___ 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] (no subject)
Hi Michai, On 28 February 2015 at 01:44, Michai Ramakers m.ramak...@gmail.com wrote: I'll pick this one up. Did you mean to change the actual option-names too? No, that was probably a mistake and my misunderstanding of the comments vs. options. What do you recommend regarding option names? It's easier to type checkin but easier to read check-in. Thanks for your other recommendation, by the way. -- --- 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] Patch for stats.wiki
Hello All, Attached is my patch for this page: https://www.fossil-scm.org/index.html/doc/trunk/www/stats.wiki It is not complete, however; I don't have access to the TH3 repo and I don't exactly know how the clone bandwidth is calculated. When cloning fossil, I see this: Clone done, sent: 1204 received: 22936695 Is clone bandwidth these two summed up and converted to MB? Thanks! -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si stat.wiki Description: Binary data ___ 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] (no subject)
Hello, On 28 February 2015 at 14:13, jungle Boogie jungleboog...@gmail.com wrote: On 28 February 2015 at 01:44, Michai Ramakers m.ramak...@gmail.com wrote: I'll pick this one up. Did you mean to change the actual option-names too? No, that was probably a mistake and my misunderstanding of the comments vs. options. ok What do you recommend regarding option names? It's easier to type checkin but easier to read check-in. Well... I would think twice before changing option names (possibly breaking scripts out there). Michai ___ 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 for src/doc.c to include log
Hello All, On 27 February 2015 at 12:52, jungle Boogie jungleboog...@gmail.com wrote: Hello All, Attached is my patch to request log in the mimetype. I realize that I had an error in my patch. Here's the correct diff. Explanation on log vs txt/text files: http://pc.net/helpcenter/answers/log_files_vs_txt_files -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si docc.patch Description: Binary data ___ 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] (no subject)
On 28 February 2015 at 21:50, Andy Bradford amb-fos...@bradfords.org wrote: Thus said Michai Ramakers on Sat, 28 Feb 2015 10:44:59 +0100: I'll pick this one up. Did you mean to change the actual option-names too? My vote is to leave checkin without the dash, and after a bit of sed, Knuth would agree: lynx --dump http://www-cs-faculty.stanford.edu/~uno/email.html | sed -e 's/[Ee]\([-]*\)mail/check\1in/g' Nothing functional was changed, just code-comment, fatal error descriptions, help-text and some generated web-content. Everything related to options and arguments was left as-is. Michai ___ 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] (no subject)
Thus said Michai Ramakers on Sat, 28 Feb 2015 10:44:59 +0100: I'll pick this one up. Did you mean to change the actual option-names too? My vote is to leave checkin without the dash, and after a bit of sed, Knuth would agree: lynx --dump http://www-cs-faculty.stanford.edu/~uno/email.html | sed -e 's/[Ee]\([-]*\)mail/check\1in/g' Andy -- TAI64 timestamp: 400054f22a45 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Wiki patch correction for local time
Hello, Since /setup_timeline uses 'local time' as the word, I'd like to request the patch applied to www/checkin_names.wiki --- www/checkin_names.wiki +++ www/checkin_names.wiki @@ -159,13 +159,13 @@ in Universal Coordinated Time (UTC). This tends to work the best for distributed projects where participants are scattered around the globe. But there is an option on the Admin/Timeline page of the web-interface to switch to local time. The bZ/b suffix on an timestamp check-in name is meaningless if Fossil is in the default mode of using UTC for -everything, but if Fossil has been switched to localtime mode, then the +everything, but if Fossil has been switched to local time mode, then the bZ/b suffix means to interpret that particular timestamp using -UTC instead localtime. +UTC instead local time. For an example of how timestamps are useful, consider the homepage for the Fossil website itself: blockquote 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] (no subject)
Thus said jungle Boogie on Fri, 27 Feb 2015 12:17:15 -0800: Can this be updated to check-in as we are graduating from checkin? This is the first time I've heard anything about ``graduating from checkin.'' Why? What purpose can making such a change serve? Especially where command arguments are involved, this seems like not a very good thing. Personally, I prefer checkin without the dash, and definitely for a command argument, adding yet one more character to type seems like a waste, not to mention all the scripts that might potentially break from such a change. Just my $0.02 Andy -- TAI64 timestamp: 400054f227cc ___ 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] (no subject)
Hi Michai, On 28 February 2015 at 05:25, Michai Ramakers m.ramak...@gmail.com wrote: Hello, On 28 February 2015 at 14:13, jungle Boogie jungleboog...@gmail.com wrote: On 28 February 2015 at 01:44, Michai Ramakers m.ramak...@gmail.com wrote: I'll pick this one up. Did you mean to change the actual option-names too? No, that was probably a mistake and my misunderstanding of the comments vs. options. ok What do you recommend regarding option names? It's easier to type checkin but easier to read check-in. Well... I would think twice before changing option names (possibly breaking scripts out there). Yes, very good point. I like the changes you did here: https://www.fossil-scm.org/fossil/ci/7c30266a4558d656 Michai -- --- 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
Re: [fossil-users] Wiki patch correction for local time
On Sat, Feb 28, 2015 at 1:03 PM, Jungle Boogie jungleboog...@gmail.com wrote: --- www/checkin_names.wiki +++ www/checkin_names.wiki @@ -159,13 +159,13 @@ in Universal Coordinated Time (UTC). This tends to work the best for distributed projects where participants are scattered around the globe. But there is an option on the Admin/Timeline page of the web-interface to switch to local time. The bZ/b suffix on an timestamp check-in name is meaningless if Fossil is in the default mode of using UTC for -everything, but if Fossil has been switched to localtime mode, then the +everything, but if Fossil has been switched to local time mode, then the bZ/b suffix means to interpret that particular timestamp using -UTC instead localtime. +UTC instead local time. I would further edit the last line, above, to: UTC instead of local time. Also, even when Fossil is using UTC for everything, the Z suffix still serves as a reminder that the timestamp is UTC, not local time. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] server.wiki patch
Hello All, Minor patch to add information about inetd on FreeBSD to the server.wiki page. I haven't tested fossil on openBSD but if its the same as freebsd, feel free to modify the patch to include that information, too. Best! -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si --- www/server.wiki +++ www/server.wiki @@ -1,6 +1,6 @@ -titleHow To Configure A Fossil Server/title +titleConfiguring a Fossil Server/title h2Introduction/h2blockquote pA server is not necessary to use Fossil, but a server does help in collaborating with peers. A Fossil server also works well as a complete website for a project. For example, the complete bhttp://www.fossil-scm.org//b website, including the page you are now reading (but excepting the download page), @@ -69,10 +69,30 @@ Obviously you will need to modify the pathnames for your particular setup. The final argument is either the name of the fossil repository to be served, or a directory containing multiple repositories. /p +p +If you are operating fossil on FreeBSD, you will need to modify your +/etc/services file with something like the following: +blockquote +pre +fossil 8080/tcp #fossil server +/pre +/blockquote + +Then you can add something like this to your /etc/inetd: +blockquote +pre +fossil stream tcp nowait.1000 user /usr/local/bin/fossil /usr/local/bin/fossil http /home/user/fossil-repos +/pre +/blockquote +p +In this example, inetd will run as user and connect over port 8080. If you +want to change the port, edit you /etc/services file and restart inetd. +/p +p p If your system is running xinetd, then the configuration is likely to be in the file /etc/xinetd.conf or in a subfile of /etc/xinetd.d. An xinetd configuration file will appear like this:/p blockquote ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users