Re: [fossil-users] Poll: which markdown extensions in fossil?
Our Situation - We use markdown in fossil to provide a generic format for simple documentation prepared by non-programmers as well as programmers. Only the document originator tends to have an on-disk copy of the files; most readers view the server copy as a wiki. Versioning of the content files is the primary reason for using embedded documentation rather than fossil wiki entry function. Style Enhancements -- Non-programmers benefit from avoiding HTML. My preference is to limit the enhancements since the result becomes yet another variation that persons writing content for different servers must accommodate. As something missing in basic markdown, support for tables in non-HTML is a desirable enhancement. At http://michelf.ca/projects/php-markdown/extra/ a list of other features is provided: Inline HTML Markdown Inside HTML Blocks Special Attributes Fenced Code Blocks Tables -- included now in fossil-markdown Definition Lists Footnotes Output Abbreviations Emphasis Backslash Escapes but they are of lesser value (in my opinion). No other style enhancements come to mind at the moment. I would discourage extensions moving much closer to word processor or page layout features but the dividing line is not sharp. Link Management --- The lack of repository-relative urls is a stumbling block that is hard to overcome. It requires testing the links in a local copy context and then rewriting them for the server context. There is resistance by non-programmers to such a complication. Link to artifact (via tip or specific hash) is a useful parallel to link to wiki page. We are not using links to other fossil components such as tickets and check-ins but I foresee that they could display the usual ticket or check-in overview. Closing --- Hope that helps, Chris Peachment On Mon, 2013-02-18 at 13:48 +0100, Natacha Porté wrote: Hello, a while back it has been brought to my attention that markdown-in-fossil behaves differently than fossil wiki when an absolute path is entered as a URI. Fossil wiki prepends it with the repository path, making absolute relative to repository root. On the other hand, current markdown-in-fossil follows the original markdown in that whatever is provided as a link is dumped directly into the href attribute, making it absolute in the usual HTML meaning. A reasonable case can be made for fossil wiki behavior, since the repository root is a more meaningful reference for anything inside the repository than the HTML root. However porting such behavior to markdown-in-fossil would deviate from original markdown. This is not a bag thing in itself, but this is a really called an extension to markdown. But then again, this is not the only link processing performed by fossil wiki. So if a case can be made for mangling absolute links, couldn't one be made for easier linking of artifacts or wiki pages? This raises an even wider question: what set of extensions should be included in markdown-in-fossil? I don't feel in a position to take such a decision by myself, so I'm asking the community here. I'm willing to provide code for any reasonable feature set, as long as there is somewhat of a consensus around it. For the reference, current markdown-in-fossil behaves like regular markdown, with table support (PHPmarkdown syntax) on top of it. The table support has been included only for my testing during the integration, since there is much code specific for it. I initially expected such a discussion to happen much sooner than that, but obviously the plan didn't survive contact with reality. Regards, Natacha Porté ___ 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] getting Fossil running on a shared host
I've just this moment faced this problem. The Linux executable available from www.fossil-scm.org does not run on Bluehost and reports an error unable to find libz.so.1 As John Found says, it is a problem related to the 64 bit environment and missing 32 bit libraries. My solution was to work at the command line shell on my Bluehost server to download the source using wget and then to use the configure command: ./configure --with-openssl=none because I do not use ssl. This was followed by: make and then a copy of the fossil executable into a local bin directory that is no my bash path. I also had to run fossil rebuild on the repositories to have the top line menu behave. On Sun, 2012-10-28 at 21:20 +0200, John Found wrote: The big problem with bluehost is that their servers run 64bit Linux, but the 32bit compatibility libraries are not installed. I faced this problem, when trying to install my CMS which is written in 32bit assembly language. (Now it runs OK: http://fresh.flatassembler.net ) Anyway, you probably need to compile fossil for 64bit or at least statically linked - I am not sure how, because I don't know C/C++, but fossil ELF executable must not use any shared libraries. Of course you need to set properly .htaccess files as well in order to properly execute cgi scripts. On Sun, 28 Oct 2012 10:52:46 -0600 Chad Perrin c...@apotheon.net wrote: I have some need for Fossil on a shared host. My first pass at trying to get it running a month or two ago, following the directions in the online documentation for Fossil SCM, met with failure. Before I give it another try, I thought it might make sense to ask for tips here. The shared hosting provider in question is Bluehost. Are there some tips and caveats that anyone can offer me for how to handle Bluehost in particular to get Fossil running? I'll need the ability to push and pull via HTTPS at least (both authenticated and anonymous pull access), preferably also SSH, and of course the usual web access stuff as well (wiki, issue tracker, source code browsing). -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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] WYSIWYG editing
On Sat, 2012-08-11 at 12:32 -0400, Richard Hipp wrote: Enhancements to Fossil to support WYSIWYG editing of wiki pages are now in the wysiwyg branch of the Fossil self-hosting repository. A sandbox repository with open permissions and with WYSIWYG editing turned on has been created at http://www.fossil-scm.org/sandbox - please experiment and provide feedback. In the Opera browser (v12.01) under Linux (Ubuntu 11.10) within a new wiki page. Test 1: 1. I moved to the end of the existing 'Empty Page' line and pressed the [enter] key to move to a new line. 2. At the start of the new line, I used the mouse to click on the numbered list icon. The cursor jumped up to the start of the wiki content and inserted the number '1.' with indentation of the first line. This is a fault; the cursor should not have jumped up. Test 2: 1. New wiki page, prior to making changes to page content, I used the mouse to click on the numbered list icon. 2. The existing 'Empty Page' line was converted into the first item in a numbered list, as expected. 3. I moved to the end of the line and pressed [enter] to continue the numbered sequence. 4. I pressed [enter] again to terminate the numbered list. The last line was changed to a normal paragraph start (recall that no text was on line except for the sequence number. This is desired behaviour. 5. I clicked on the numbered list icon again. The browser crashed. End of tests. ___ 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] Looking for a name for Android Fossil client...
On Sat, 2012-06-23 at 14:14 +0200, Stephan Beal wrote: On Sat, Jun 23, 2012 at 1:23 PM, Miles Fidelman mfidel...@meetinghouse.net wrote: Stephan Beal wrote: Fossiloid was actually my very first choice, but has the drawback that the oid suffix normally refers to a diminutive/lesser form, like meteor vs. meteoroid and human vs. humanoid. (Yeah, i'm being pedantic. :/) Sure, but doesn't that go along with being on a smaller device? :-) Very good point. Hmmm. Or Fossilite, since it is a light client. +1 since it merges Fossil and Sqlite quite nicely. And its easy to say. God forbid that you ever produce an iPhone or Windows Mobile version, but at least the name could be reused. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] assign ticket to file(s) or abusing Fossil a bit
It looks to me like you could add a new field to the 'ticket' table, say PatientIdentifier of type text, and enter its value as part of the ticket add function. A new report selecting on this new field would provide the view of all tickets ordered by PatientIdentifier. The missing part is some way to pass the patient id to the report so that it selects only tickets for the given patient. You might need to hack the report menu source code to permit entry of one (or more) parameters when the report is selected. Regards, Chris On Sun, 2012-02-26 at 12:13 +0100, Gour wrote: Hello! Being (again) interested to try to use Fossil for all my DVCS needs, I got idea to 'abuse' it even further and use to track records of our counseling homeopathy patients...The idea is to have single file per patients with more detailed data about each client and then have tickets connected with the files for the treatment history (think about poor man's Electronic Medical Record (EMR). Now I just wonder if there is some easy way to get report which would show all the tickets connected with certain file and/or to assign ticket to certain file or to tag tickets somehow that we could see all the 'medical episodes' connected with certain patient? Sincerely, Gour ___ 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] Login Group Confusion
On Thu, 2012-02-23 at 08:54 -0500, Richard Hipp wrote: I can't tell from the text that follows if you are setting up the login-groups right or not. The correct way to do it is as follows: A. Login via browser to b.fossil. Go to the /Admin/Login-Groups screen and join a.fossil. B. Login via browser to c.fossil. Go to the /Admin/Login-Groups screen and join a.fossil. C. Login via browser to d.fossil. Go to the /Admin/Login-Groups screen and join a.fossil. Is that what you are doing? I believe so. There is not much discretion available on this form. A small point of confusion is that I used b.fossil as the reference and joined a, c, and d to it. For each join action, the entries consisted of: Repository filename in group to join: [path to repo]/b.fossil Login on the above repo: my logged in user id Password: same as returned by the fossil init b.fossil Name of login-group: New Login Group for a,c but blank for d. ___ 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] documentation clarification
On Wed, 2012-02-01 at 09:03 -0500, Leo Razoumov wrote: On Wed, Feb 1, 2012 at 07:08, Richard Hipp d...@sqlite.org wrote: The clock according to the D card of the artifact. In other words, you can keep changing the value of a tag and the latest version always wins. If two people change the value of a tag while disconnected, then later sync, the latest change wins. Let say, the clock on your client machine is accurate but on my machine the clock is one year behind (slight exaggeration-:). You set a tag a month ago and I changed it today and then we sync. Your tag still wins because my clock is hopelessly behind! The problem is that D card value is set at the disconnected clients and there are no guarantee that all these clocks are synchronized. Generally speaking, one cannot rely on uncoordinated clocks to establish sequence of events. I think that was one of the reasons git does not use timestamps while building its DAG. Hopefully, this issue is of no practical importance, for one can always correct errors later on by pushing yet another tag. --Leo-- The wonders of the internet include the Network Time Protocol (http://www.ntp.org/) and I think all major operating systems have a mechanism for enabling it, if that is not the default. It is then possible to have synchronised time keeping to a meaningful level of precision. I can't speak for MS-Windows or MacOS but Ubuntu Linux uses NTP by default. ___ 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] Technical Proposal: Supporting Extended Markup in Fossil
I REALLY like the appearance of the markdown output. I had not appreciated the limitations of standard fossil wiki markup since I generally pay more attention to content than to appearance. And the raw text is quite readable in its original form. Taking a suggestion posed in the original document, I placed the entire content of 'fossilmarkup.txt' into the standard fossil sandbox to see what happens. I think there is still work to be done on the proposal. Standard fossil causes the following: 1. contents surrounded by backticks are removed. 2. footnote annotations are duplicated. 3. paragraph separations failed in section 4 Rendering with the result that sections 4, 5, and start of 6 are merged into one paragraph. While it IS readable (with corrections for the above), the standard fossil display of the markdown text encourages one to upgrade. As an additional suggestion, it might be useful if the wrapper left a note in the output as rendered by standard fossil to identify the intended renderer. Regards, Chris On Sun, 2012-01-15 at 09:08 +0100, Martin Hofmann wrote: ... Linked below is a proposal of how one could implement support for extended markup syntaxes (yes, multiple of them), interoperate with current Fossil programs and repositories, and package markup syntaxes into loadable modules. ... The proposal is titled: Extended Markup in Fossil, find it here: http://dl.dropbox.com/u/13455033/fossilmarkup.html (The HTML doc is of course derived form a Markdown-text which I also have put into my public dropbox; so maybe this is another example for the usefulness of a good wiki markup syntax ...:) http://dl.dropbox.com/u/13455033/fossilmarkup.txt ___ 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] event changes don't appear in the timeline
+1 On Fri, 2011-12-02 at 16:19 +0100, Lluís Batlle i Rossell wrote: Hello, event changes don't appear in the timeline. Maybe they should appear, as ticket or commit changes appear? Regards, Lluí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] Quickref available for fossil
Thank you for providing a great assistance to novice users.
I and the eight person team with which I work are such and
this will be a useful addition.
Some notes:
1. Not all readers will be programmers and not all will have
English as first language. The combination makes for extra
work to understand some of the descriptions and examples:
sync - synchronise when not used as a parameter
deltas - changes - this is an expression with math origins
and thus even more obtuse to artists :-)
2. Under Move/mv, do the Safely and unambiguously...
instructions work under MS-Windows? I don't use MS-Windows so
I can not say for sure.
3. Only the checkin ('ci') and commit ('co') commands have been
abbreviated. Others use the full word for the command. Perhaps
a small note at the end about the ability to abbreviate would
be a reminder to those with greater experience.
4. Page 2 Stash command has a typo:
stash for later retrival
should be
stash for later retrieval
5. Page 2 Controlled Docs Mechanism description mentions
Can also server .wiki files using wiki syntax
and an example would be useful for non-programmers.
Thanks again.
Chris
On Thu, 2011-11-24 at 22:43 -0700, Matt Welland wrote:
I'm teaching a class on using fossil next week and put together a
quick ref sheet to help folks get going. I haven't seen any other
quick ref sheets for fossil so maybe this will be of use to others.
PDF:
http://www.kiatoa.com/cgi-bin/fossils/opensrc/doc/tip/docs/fossil-quickref.pdf
Opendoc:
http://www.kiatoa.com/cgi-bin/fossils/opensrc/doc/tip/docs/fossil-quickref.odt
Feedback, corrections, suggestions all much appreciated.
Cheers,
Matt
-=-
___
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] Quickref available for fossil
I revealed my own ignorance with this comment:
3. Only the checkin ('ci') and commit ('co') commands have been
abbreviated. Others use the full word for the command. Perhaps
a small note at the end about the ability to abbreviate would
be a reminder to those with greater experience.
I should have said:
3. Only the checkin ('ci') and checkout ('co') commands have been
abbreviated. Others use the full word for the command. Perhaps
a small note at the end about the ability to abbreviate would
be a reminder to those with greater experience.
I accept that both are synonyms rather than abbreviations.
On Thu, 2011-11-24 at 22:43 -0700, Matt Welland wrote:
much good stuff...
___
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] Need to configure an empty repository from command line
Thank you for providing the key concept to use the configuration
import command with a generated configuration file.
I had been attempting to alter the repository configuration one
field at a time using the command line fossil operations but this
is a much simpler approach.
I have the scripting done by a C program (in place of your Ruby)
but the principle is the same.
Steps:
1. generate configuration.txt
2. fossil new repo name
3. fossil configuration import configuration.txt
4. Repeat from 1. as needed.
Done.
On Mon, 2011-11-21 at 09:04 +, Ben Summers wrote:
On 21 Nov 2011, at 01:13, Richard Hipp wrote:
On Sun, Nov 20, 2011 at 7:56 PM, Chris Peachment ch...@ononbb.com wrote:
I'm using fossil version 1.20 on Linux for both server and client
computers.
I want to use fossil command line instructions to initialise an
empty repository. I use:
fossil new test.fossil
but I can not find a command to provide the project-name value to
be stored in the config table.
There isn't one - or at least not a simple one. I always configure
using the web interface: just run fossil ui test.fossil and manually
configure it that way.
If you definitely, positively must do your configuration from the
command line, it can be done using raw SQL. Probably just a single
INSERT statement. But I'd have to go look up exactly what that INSERT
statement would be. May I suggest: Configure a dummy repository using
fossil ui and then look in the CONFIG table of the repository database
to see where the project name got inserted. It should be obvious from
there what you need to do to insert that name yourself.
While it seems a bit odd to be contradicting Richard about his own software,
I've written a simple script to create blank repositories for our clients
which sets the project name using the fossil configuration import command.
When you're creating lots of repositories, it's very boring and error-prone
if you don't script everything.
You have to write a configuration file before using the import command, and
although you're unlikely to want to write it by hand, the format is quite
simple. There's a snippet of Ruby code below which I think should get you
started (tip: examine the output of fossil configuration export first),
email me off list if anyone wants the entire repo generating script.
Ben
def config_entry(name, value)
l = %Q!#{Time.now.to_i} '#{name}' value '#{value}'!
config /config #{l.length}\n#{l}\n
end
File.open(mcr.config.tmp, w) do |f|
f.write config_entry('project-name', #{CLIENT_FULLNAME})
f.write config_entry('project-description', #{CLIENT_FULLNAME} ONEIS
Plugins)
f.write config_entry('index-page', /wiki?name=home)
end
system fossil configuration -R #{REPO_FILENAME} import mcr.config.tmp
File.unlink(mcr.config.tmp)
--
http://bens.me.uk/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Need to configure an empty repository from command line
I'm using fossil version 1.20 on Linux for both server and client
computers.
I want to use fossil command line instructions to initialise an
empty repository. I use:
fossil new test.fossil
but I can not find a command to provide the project-name value to
be stored in the config table.
The following instruction does not have the same effect as
using the fossil ui web interface to enter this value.
fossil sqlite3 test.fossil insert into config values ('project-name',
'Test Repository', current_timestamp) -R test.fossil
One consequence of using the insert statement that cloning the
repository does not transfer the project-name.
Closed ticket 8473eeb9ffb012e1db8597d97c9f7fdde340485e shown at
http://fossil-scm.org/index.html/tktview?name=8473eeb9ff
refers to this clone behaviour but does not describe how the
repository was created, so it is not clear if the above action
was the cause of the behaviour seen prior that ticket.
As secondary issues, I can not find commands to supply the
project-name and user info fields.
And it would be nice to insert a wiki page (specifically the
home page) from the command line too.
Thanks for any assistance.
Chris Peachment
___
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] Need to configure an empty repository from command line
As indicated in my statements below your insert, I have tried
using the raw SQL approach. The insert statement shown there
was derived from looking at the config table of a dummy
repository.
The motivation for using command line entries is that I'm doing
it for 25 repositories at the moment and anticipating that
number increasing to about 100. Each repository has a similar
name (e.g. F-100, F-110, F-120, ...) and a similar set of users.
The server directory with these repositories is a library for
use by non-programmers in the creation and archiving of text
and word processing documents on a project basis. Each repository
is a separate project.
So I created a C program to read from another sqlite database
and generate the fossil commands. By updating the control
database contents, I can continue the semi-automated creation
with less risk of missing some configuration step on one of
many repositories.
On Sun, 2011-11-20 at 20:13 -0500, Richard Hipp wrote:
On Sun, Nov 20, 2011 at 7:56 PM, Chris Peachment ch...@ononbb.com
wrote:
I'm using fossil version 1.20 on Linux for both server and
client
computers.
I want to use fossil command line instructions to initialise
an
empty repository. I use:
fossil new test.fossil
but I can not find a command to provide the project-name value
to
be stored in the config table.
There isn't one - or at least not a simple one. I always configure
using the web interface: just run fossil ui test.fossil and
manually configure it that way.
If you definitely, positively must do your configuration from the
command line, it can be done using raw SQL. Probably just a single
INSERT statement. But I'd have to go look up exactly what that INSERT
statement would be. May I suggest: Configure a dummy repository
using fossil ui and then look in the CONFIG table of the repository
database to see where the project name got inserted. It should be
obvious from there what you need to do to insert that name yourself.
The following instruction does not have the same effect as
using the fossil ui web interface to enter this value.
fossil sqlite3 test.fossil insert into config values
('project-name',
'Test Repository', current_timestamp) -R test.fossil
One consequence of using the insert statement that cloning the
repository does not transfer the project-name.
Closed ticket 8473eeb9ffb012e1db8597d97c9f7fdde340485e shown
at
http://fossil-scm.org/index.html/tktview?name=8473eeb9ff
refers to this clone behaviour but does not describe how the
repository was created, so it is not clear if the above action
was the cause of the behaviour seen prior that ticket.
As secondary issues, I can not find commands to supply the
project-name and user info fields.
And it would be nice to insert a wiki page (specifically the
home page) from the command line too.
Thanks for any assistance.
Chris Peachment
___
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] More thoughts on locks
I'm a novice Fossil user working in a small group with need to track both text and binary files. It seems to me that locks are nice to have for text files since 3 way diffs can be merged at relatively little cost. But inability to merge binary files might mean painful hand merging based on side by side comparisons for word processing documents or presentation slides, or based on repeating the edits for image files. So a lock would provide immediate warning when attempting checkout that someone else is probably touching the file. Out of band communication would be needed to gain access - not a bad thing and better than proceeding blindly. Locking artefacts provides a good way to split the chain of past and current versions. Locking should be optional to retain current behaviour for those users wanting it. How would the person doing the checkout that created the lock know this fact, as encouragement to avoid long lockout periods? How would their repository know they owned the lock? Since a commit generates a new artefact, how does the old, locked one, get unlocked? On Thu, 2011-10-20 at 19:22 +0200, Lluís Batlle i Rossell wrote: Thinking as if we had to implement locks some day... I just thought that we could have locks working not on file-paths-in-branch, but on artifacts. That would expand well to multiple branches. Then, if anyone gets the lock, and commits a new version, it could get locked automatically too, expanding the list of artifacts needing lock. Those artifacts that 'require lock' for edition could be checked out read-only. The list of locked artifacts could expand similar to the shun list, that can be told to be updated on autosync. And the list of lock owners too. Keeping the default remote as the source of locks. And apart, not requiring a locks implementation, there could be a fossil default-off option to simply check out binary files readonly (fossil seems to know what file is binary and what not). That would put a step before binary-file editions, inviting to team communication. If anyone think locks could help in their use of fossil, that chould give an opinion on this. I work either in a small team or alone, so I'm not very representative on this. ___ 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
