[fossil-users] Fossil ls not as documented
Hello, fossil ls is documented as: Usage: fossil ls ?OPTIONS? ?VERSION? ?FILENAMES? The ?VERSION? led me to believe I could get info about older revisions this way. After some problems I resorted to source-diving and it seem that fossil ls is purely about the current checkout, and there is no version in its arguments. Have I interpreted this correctly? I even found when the confusing string was introduced: http://fossil-scm.org/index.html/info/9ba8a393fcc569b2 Is there any command line way to get the files and times of a revision? Right now it seems I would need to parse the output of this to get the information I need: echo 'GET /fileage?name=ae01244396' | fossil http /Peter ___ 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 dbstat vs /stat
Hi Stephan, On 24 February 2015 at 18:29, Stephan Beal sgb...@googlemail.com wrote: i.e. CLI vs WWW. @Jungle, some of those differences are expected (or not unexpected), by the way, namely the Database Stats. Sorry to have mislead this and made it difficult to follow! Yes, I meant my dbstats vs what shows on web for fossil-scm.org. As long as both match on a real repo that I own, that's great. -- --- 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] JavaScript error in div class=content
On 2/25/15, Kai Lauterbach kla...@web.de wrote:
Hi,
in my other thread I asked for help to insert a navigation bar into my
wiki pages.
During this work I got serious error messages in my browser console:
Uncaught SyntaxError: Unexpected token }
It seems to be that there is a typo in th javascript function gebi().
There is a trailing } without the opening bracket in the function.
The code beyond shows a small sourcecode sniplet from one of my wiki pages.
---
div class=content
script
function gebi(x){
^- Opening curly brace
if(/^#/.test(x)) x = x.substr(1);
var e = document.getElementById(x);
if(!e) throw new Error(Expecting element with ID +x);
else return e;}
^- Close curly brace
/script
What am I overlooking?
--
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
Re: [fossil-users] Fossil 1.30 : db_record_repository_filename() never writes ckout to REPOSITORY.config
Wow! Already fixed -- Execute 'optional' SQL statements in their original order https://www.fossil-scm.org/fossil/info/24d7ebe12afa2f72 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] Fossil source download naming scheme
On Wed, 25 Feb 2015, Stephan Beal wrote: On Tue, Feb 24, 2015 at 9:11 PM, Richard Hipp d...@sqlite.org wrote: So it seems like having dates on the download would be more meaningful than having a made-up version number. No? With a date, at least you know about how old the code is. What information does a made-up version number provide? How is that better than a date? FWIW, that's the approach i've taken for all but one of my own projects the past 15 years. Version numbers, _unless_ they are accompanied by a strict set of compatibility rules involving API- and/or binary compatibility, are _absolutely meaningless_. [joke] If we all were paleontologists, we could use the names of fossil animals for significant milestones of Fossil SCM http://www.fossilrecord.net/ http://www.fossilrecord.net/dateaclade/index.html http://www.fossilrecord.net/fossilrecord/download.html Sergei___ 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 ls not as documented
Hi Peter, On 25 February 2015 at 04:49, Peter Spjuth peter.spj...@gmail.com wrote: The ?VERSION? led me to believe I could get info about older revisions this way. After some problems I resorted to source-diving and it seem that fossil ls is purely about the current checkout, and there is no version in its arguments. Have I interpreted this correctly? I even found when the confusing string was introduced: http://fossil-scm.org/index.html/info/9ba8a393fcc569b2 Have you tested with that available download, one the one just before that to see what fossil ls does then compared to what it does with current? -- --- 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] Fossil source download naming scheme
On Tue, Feb 24, 2015 at 8:03 PM, jungle Boogie jungleboog...@gmail.com wrote: For my day job, version numbers in ANY capacity are out of the equation (NOT my choice). The project in question either in trunk/head or its in some branch. It pretty much means filing bug reports are useless since we can't really identify when an issue first occurred. I'd be happy for a version number, svn rev number, or a date in my work's product. Too bad it's not my decision to change this, although I've filed a bug report to have it included. ;) So, users of your products have no way to identify what release they are using? ___ 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 source download naming scheme
On 25 February 2015 at 11:03, Ron W ronw.m...@gmail.com wrote: On Tue, Feb 24, 2015 at 8:03 PM, jungle Boogie jungleboog...@gmail.com wrote: For my day job, version numbers in ANY capacity are out of the equation (NOT my choice). The project in question either in trunk/head or its in some branch. It pretty much means filing bug reports are useless since we can't really identify when an issue first occurred. I'd be happy for a version number, svn rev number, or a date in my work's product. Too bad it's not my decision to change this, although I've filed a bug report to have it included. ;) So, users of your products have no way to identify what release they are using? Unfortunately, that's correct. I have no idea why we don't include some version or revision number in our product. The customer likely won't care but for bug reporting, it's ideal as when the bug is reviewed, QA knows what to test against. -- --- 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] Fossil source download naming scheme
On Tue, Feb 24, 2015 at 8:00 PM, Richard Hipp d...@sqlite.org wrote: On 2/24/15, Ron W ronw.m...@gmail.com wrote: [Managers] associate dates with deadlines, so version numbers remove a source of panic. Fair enough. I'll migrate from dates to version numbers in the next release. I was only responding to Stephan's comment about the uselessness of version numbers. Whether Fossil identifies releases via a version number or a date/time stamp doesn't matter to me or my team. On the other hand, most applications my team and I (and other coworkers) use do use version numbers. (Some even use x.y.z.n where n appears to be either a commit number (al a SVN) or build number from a master build server.) ___ 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] Tags and unhide
On Wed, Feb 25, 2015 at 3:37 AM, Gaurav M. Bhandarkar gaurav.a...@gmail.com wrote: How is the output lines, eg 16:06 Edit [72114148]: Edit check-in comment. (user: drh) [details], related to most recent tags. For a check-in (or a ticket), comment is a tag. The comment tag also has a value, which is the test of the comment. (Beside being symbolic names, tags may also have values.) ___ 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 source download naming scheme
On Wed, Feb 25, 2015 at 11:13:22PM +0300, Sergei Gavrikov wrote: If we all were paleontologists, we could use the names of fossil animals for significant milestones of Fossil SCM What fossil are of interested other than Trilobites?! Joerg ___ 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] Tags and unhide
Thus said Gaurav M. Bhandarkar on Wed, 25 Feb 2015 14:07:08 +0530: if a branch is marked as closed, it is (by default) hidden Oh, I think I understood the significance of unhide. Thanks for explaining. Unless I have missed something, closing a branch does not hide the branch. It does remove it from the list of ``open'' branches search, however, that is not what the unhide button is for. The unhide button will reveal commits in the timeline that have the hidden tag added to them. For example, click unhide here: https://www.fossil-scm.org/index.html/timeline?c=20015206bc While this particular branch is closed, it is not the fact that it is closed that makes it hidden, but rather the presence of a hidden tag that was added here: https://www.fossil-scm.org/index.html/info/829d88c0af42c450 Here are examples of a ``closed'' branch that are visible: https://www.fossil-scm.org/index.html/timeline?c=2014-04-22+10:01:05 https://www.fossil-scm.org/index.html/timeline?c=2015-02-23+23:40:53 Clicking unhide for the 2 previous links will reveal nothing. Andy -- TAI64 timestamp: 400054ee3ea2 ___ 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 source download naming scheme
Archeopteryx (proto-bird) On Wed, Feb 25, 2015 at 1:12 PM, Joerg Sonnenberger jo...@britannica.bec.de wrote: On Wed, Feb 25, 2015 at 11:13:22PM +0300, Sergei Gavrikov wrote: If we all were paleontologists, we could use the names of fossil animals for significant milestones of Fossil SCM What fossil are of interested other than Trilobites?! Joerg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] html quote bug in info.c
Looks like %W is used instead of %w in rendering checkin comments. Any
checkin comment containing the character '' will be rendered
incorrectly.
This patch (against b0febccc4e) cleans it up and corrects the comment
in printf.c. Hope it formats correctly!
Index: src/info.c
==
--- src/info.c
+++ src/info.c
@@ -598,14 +598,14 @@
}else{
@ trthUser:/thtd
hyperlink_to_user(zUser,zDate,/td/tr);
}
if( zEComment ){
- @ trthEditednbsp;Comment:/thtd
class=infoComment%!w(zEComment)/td/tr
- @ trthOriginalnbsp;Comment:/thtd
class=infoComment%!w(zComment)/td/tr
+ @ trthEditednbsp;Comment:/thtd
class=infoComment%!W(zEComment)/td/tr
+ @ trthOriginalnbsp;Comment:/thtd
class=infoComment%!W(zComment)/td/tr
}else{
- @ trthComment:/thtd class=infoComment%!w(zComment)/td/tr
+ @ trthComment:/thtd class=infoComment%!W(zComment)/td/tr
}
if( g.perm.Admin ){
db_prepare(q2,
SELECT rcvfrom.ipaddr, user.login, datetime(rcvfrom.mtime)
FROM blob JOIN rcvfrom USING(rcvid) LEFT JOIN user USING(uid)
Index: src/printf.c
==
--- src/printf.c
+++ src/printf.c
@@ -206,12 +206,12 @@
/*
** Return an appropriate set of flags for wiki_convert() for displaying
** comments on a timeline. These flag settings are determined by
** configuration parameters.
**
-** The altForm2 argument is true for %!w (with the ! alternate-form-2
-** flags) and is false for plain %w. The ! indicates that the text is
+** The altForm2 argument is true for %!W (with the ! alternate-form-2
+** flags) and is false for plain %W. The ! indicates that the text is
** to be rendered on a form rather than the timeline and that block markup
** is acceptable even if the timeline-block-markup setting is false.
*/
static int wiki_convert_flags(int altForm2){ static int wikiFlags = 0;
___
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] select menus and back button
On Wed, Feb 25, 2015 at 7:42 PM, Andy Goth andrew.m.g...@gmail.com wrote: Easiest way to demonstrate this problem is to go to: http://www.fossil-scm.org/index.html/timeline?y=ci which should initially show Without Files. Select With Files, then press the browser's Back button. At this point files will not be shown, but the select menu will indicate With Files is currently selected. As best I can recall, this is the same behavior I've seen with many other web apps, including a few I worked on. My work around for this was to include a Javascript function, triggered by the onload event, to reset selection menus to the options that match the page content. ___ 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] select menus and back button
On 2/25/15, Ron W ronw.m...@gmail.com wrote: As best I can recall, this is the same behavior I've seen with many other web apps, including a few I worked on. My work around for this was to include a Javascript function, triggered by the onload event, to reset selection menus to the options that match the page content. I don't think the Back button triggers onload. At least it didn't in the experiment I tried a few minutes ago... -- 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
Re: [fossil-users] html quote bug in info.c
On 2/25/15, aspect asp...@abstracted-spleen.org wrote:
Looks like %W is used instead of %w in rendering checkin comments. Any
checkin comment containing the character '' will be rendered
incorrectly.
This patch (against b0febccc4e) cleans it up and corrects the comment
in printf.c. Hope it formats correctly!
See the complete fix at https://www.fossil-scm.org/fossil/info/3b92154af8d44c0e
Index: src/info.c
==
--- src/info.c
+++ src/info.c
@@ -598,14 +598,14 @@
}else{
@ trthUser:/thtd
hyperlink_to_user(zUser,zDate,/td/tr);
}
if( zEComment ){
- @ trthEditednbsp;Comment:/thtd
class=infoComment%!w(zEComment)/td/tr
- @ trthOriginalnbsp;Comment:/thtd
class=infoComment%!w(zComment)/td/tr
+ @ trthEditednbsp;Comment:/thtd
class=infoComment%!W(zEComment)/td/tr
+ @ trthOriginalnbsp;Comment:/thtd
class=infoComment%!W(zComment)/td/tr
}else{
- @ trthComment:/thtd
class=infoComment%!w(zComment)/td/tr
+ @ trthComment:/thtd
class=infoComment%!W(zComment)/td/tr
}
if( g.perm.Admin ){
db_prepare(q2,
SELECT rcvfrom.ipaddr, user.login, datetime(rcvfrom.mtime)
FROM blob JOIN rcvfrom USING(rcvid) LEFT JOIN user
USING(uid)
Index: src/printf.c
==
--- src/printf.c
+++ src/printf.c
@@ -206,12 +206,12 @@
/*
** Return an appropriate set of flags for wiki_convert() for displaying
** comments on a timeline. These flag settings are determined by
** configuration parameters.
**
-** The altForm2 argument is true for %!w (with the ! alternate-form-2
-** flags) and is false for plain %w. The ! indicates that the text is
+** The altForm2 argument is true for %!W (with the ! alternate-form-2
+** flags) and is false for plain %W. The ! indicates that the text is
** to be rendered on a form rather than the timeline and that block markup
** is acceptable even if the timeline-block-markup setting is false.
*/
static int wiki_convert_flags(int altForm2){ static int wikiFlags = 0;
___
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] select menus and back button
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The new select menus don't play well with the back button in Firefox 36.0, likely other versions too. After pressing back, the menu shows not the old option but rather the option that was selected in order to transition to the new page. For example, start with Check-ins, then select Tags, then Tech Notes. Next press Back, and while tag edits are shown, the menu still shows Tech Notes. Pressing Back again shows checkins, but the menu shows Tags. - -- Andy Goth | andrew.m.goth/at/gmail/dot/com -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJU7mTcAAoJELtYwrrr47Y4XBYH/36DYrfMl7vfWd2zE+4fBgd5 t4Sm70j2z7vzVYkUfRW6y6Fwbkc92sJtmu1fiD0wCeyFNgZZ96vf/G0qJ2RG0XwX 4q4ODQZLUMZwPPY7AJzOaGyI6z3xPN2AJpPk+aWti+YnNgI/n5SH/ISP/p253vw6 YQ35UUEXSUqg/4kwqUnZHImevfBi6DbT72Z9SFxjgHZBRUuxXXjBxKtfLFZiXTD1 /Nwg+Vew5LEMr4EC471wpdxPWVeZ8iPPjQJbwwbRppdRz4L9NRl7Ot+Yq7kDhW46 ccBoJLRJkGr+ts0skbvsXdr00KCl2JBYSUPg0g0tHerKyBmjrrk+/256iZeNYzU= =eNSs -END PGP SIGNATURE- ___ 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] select menus and back button
Hi Andy, On 25 February 2015 at 16:12, Andy Goth andrew.m.g...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The new select menus don't play well with the back button in Firefox 36.0, likely other versions too. After pressing back, the menu shows not the old option but rather the option that was selected in order to transition to the new page. For example, start with Check-ins, then select Tags, then Tech Notes. Next press Back, and while tag edits are shown, the menu still shows Tech Notes. Pressing Back again shows checkins, but the menu shows Tags. This wasn't the case for me on firefox 36 windows 7 home premium 64bit edition. I did observe the with/out files section remains as with files as you navigate to other options, but only check-ins actually have files to display. - -- Andy Goth | andrew.m.goth/at/gmail/dot/com -- --- 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] select menus and back button
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/25/2015 6:32 PM, jungle Boogie wrote: On 25 February 2015 at 16:12, Andy Goth andrew.m.g...@gmail.com wrote: The new select menus don't play well with the back button in Firefox 36.0, likely other versions too. After pressing back, the menu shows not the old option but rather the option that was selected in order to transition to the new page. For example, start with Check-ins, then select Tags, then Tech Notes. Next press Back, and while tag edits are shown, the menu still shows Tech Notes. Pressing Back again shows checkins, but the menu shows Tags. This wasn't the case for me on firefox 36 windows 7 home premium 64bit edition. Point for point, that's exactly my same configuration. I did observe the with/out files section remains as with files as you navigate to other options, but only check-ins actually have files to display. Easiest way to demonstrate this problem is to go to: http://www.fossil-scm.org/index.html/timeline?y=ci which should initially show Without Files. Select With Files, then press the browser's Back button. At this point files will not be shown, but the select menu will indicate With Files is currently selected. This is just another demonstration of the underlying problem I described in my initial email. - -- Andy Goth | andrew.m.goth/at/gmail/dot/com -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJU7mwDAAoJELtYwrrr47Y48G4IAK41l9UZGiEDPnPvZHS14W58 lR4nBrFjguoKsU7j1R4vCZ1a7G0yMiWxBm4obVVwWf0KNITxJ5l8CVNLJ7Sa3nEP Mf3ZkszXQ3ozQBcHBkd7jR8u+4o7HcMR1/iGBgKCx80osBY7UKNWZvGrLHZrY/Mu eUGHxHkpjDWBxeNFed2XmcyzwPId4nH91Tx0ID+Wwv2sbgKqj4bzn/wFeYaAVT2c mtiwvTAj+prx4JZucgwTXYm0uFli4chCOJhDK4Q7zQ+OV/0bwukAWcthCKhwjsE7 UObFOPiNKVwSmgsbRKoG4RsNQ6tIC7QwM/9ztOuNduhdhQxwZiPI2FqcbJywa7I= =VFjt -END PGP SIGNATURE- ___ 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] select menus and back button
Hi Andy, On 25 February 2015 at 16:42, Andy Goth andrew.m.g...@gmail.com wrote: Easiest way to demonstrate this problem is to go to: http://www.fossil-scm.org/index.html/timeline?y=ci which should initially show Without Files. Select With Files, then press the browser's Back button. At this point files will not be shown, but the select menu will indicate With Files is currently selected. Yes, this is true on chrome and firefox. This is just another demonstration of the underlying problem I described in my initial email. You're right, I can reproduce this more accurately now with chrome, too. -- --- 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] Tags and unhide
Tags are symbolic names that may or may not be propagate Yes. But what does the page : https://www.fossil-scm.org/index.html/timeline?n=50y=gv=0 mean by 50 most recent tags ? How is the output lines, eg 16:06 Edit [72114148]: Edit check-in comment. (user: drh) [details], related to most recent tags. Note that I went to the page by selecting tags from timeline, I didn't manually generate that URL. Also, what does selecting tags from the drop-down menu means when you are viewing a branch: Eg. when you're viewing the timeline of json branch, https://www.fossil-scm.org/index.html/timeline?n=100r=json selecting tags from drop-down menu shows: 0 tags related to json if a branch is marked as closed, it is (by default) hidden Oh, I think I understood the significance of unhide. Thanks for explaining. -Gaurav On Wed, Feb 25, 2015 at 1:07 AM, bch brad.har...@gmail.com wrote: Tags are symbolic names that may or may not be propagate -- a branch name is an example of a propagating tag, and a non-propagating tag may be (for example) a tag that marks a specific commit as a release (see: http://fossil-scm.org/index.html/timeline?r=version-1.30) -- if a branch is marked as closed, it is (by default) hidden. The idea is that it's closed because we don't generally care about it, and therefore to display it is just to clutter the timeline. Of course, as is fossils model, no content is actually deleted or modified. On 2/24/15, Gaurav M. Bhandarkar gaurav.a...@gmail.com wrote: Hi, What does selecting Tags in Timeline actually do? I was expecting to see the list of non-propagating tags but I don't understand how I could use the output I see. Also, what does unhide actually do? Why do I need to explicitly click unhide to see any output on this page: https://www.fossil-scm.org/fossil/timeline?n=100r=mistake Thanks. -Gaurav ___ 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
