Re: [fossil-users] Questions about using "tag"

2012-11-23 Thread Jacek Cała
2012/11/23 Richard Hipp fossil commit -f --tag release --tag version-3.7.15 --bgcolor "#d0c0ff' > > This hint (and others you mentioned later in your e-mail) is really useful to know. IMHO it is much more important to update documentation with such {clever hints/best practices} than invest

Re: [fossil-users] Fwd: Fossil design error and possible ways to fix it

2012-11-23 Thread Jacek Cała
Personally, I don't mind if you go for option (1). From the fossil timeline you mentioned ( http://www.fossil-scm.org/fossil/timeline?c=2012-11-21+16%3A28%3A03) it seems that it's not a big issue at all. I believe that all relevant comments can be easily edited by hand for all those who really need

Re: [fossil-users] Fossil design error and possible ways to fix it

2012-11-23 Thread Steve Havelka
On 11/22/2012 05:05 AM, Richard Hipp wrote: > (2) Always assume text/x-fossil-wiki for check-in comments that were > entered prior to some cut-off date (say 2012-12-01) and assume > text/plain thereafter. Perhaps the cut-off date can be changed for > individual repositories using a configuration o

Re: [fossil-users] Questions about using "tag"

2012-11-23 Thread Richard Hipp
On Thu, Nov 22, 2012 at 9:19 AM, Gilles wrote: > Hello > > I checked the "help" section and googled for more infos, but am > still a bit unclear at how to use the "tag" option to add tags to a > given check-in: > > 1. Am I correct in understanding that the "tag" command can be either > us

Re: [fossil-users] th1 documentation

2012-11-23 Thread Richard Hipp
On Fri, Nov 23, 2012 at 5:17 AM, wrote: > > Hi, > > is there a recent and complete document on th1? I know of > http://www.sqliteconcepts.org/**THManual.pdf, > but that does not list all events and actions th1 can take. > > There is no documentation o

Re: [fossil-users] Fwd: Fossil design error and possible ways to fix it

2012-11-23 Thread Richard Hipp
On Fri, Nov 23, 2012 at 5:15 AM, wrote: > Hi, > > I think the cleanest solution is to extend the artifact format by adding > optional mimetype fields to the > end of C and J cards (solution 3a) > > Together with this let people choose at ticket/comment creation if its > text (default) or html. >

[fossil-users] th1 documentation

2012-11-23 Thread fossil-mail
Hi, is there a recent and complete document on th1? I know of http://www.sqliteconcepts.org/THManual.pdf , but that does not list all events and actions th1 can take. thanks, M. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org h

[fossil-users] Fwd: Fossil design error and possible ways to fix it

2012-11-23 Thread fossil-mail
Hi, I think the cleanest solution is to extend the artifact format by adding optional mimetype fields to the end of C and J cards (solution 3a) Together with this let people choose at ticket/comment creation if its text (default) or html. For the backward compatibility: Do old fossil bui