On 11/22/2012 5:05 AM, Richard Hipp wrote:
Fossil understands check-in comments and ticket text to be Wiki/HTML.
Let's say that the mimetype is text/x-fossil-wiki. This approach
worked well for us on CVSTrac (which was where many of the ideas in
Fossil originated) because it allowed hyperlinks
On Mon, Nov 26, 2012 at 2:31 PM, Ross Berteig r...@cheshireeng.com wrote:
On 11/22/2012 5:05 AM, Richard Hipp wrote:
Fossil understands check-in comments and ticket text to be Wiki/HTML.
Let's say that the mimetype is text/x-fossil-wiki. This approach
worked well for us on CVSTrac (which
IMO this should be resolved per-server configuration. Consider the
risk of XSS attacks: simply treating all comments as text/plain
automatically mitigates any past XSS attack attempts. Granted, XSS
attacks are not very likely given that few users can be expected to
have commit access...
I would
In my workflow each commit is associated with a ticket. This provides
me with requirement tracking and traceability from the
requirements/tasks/defects stored in tickets to the code or data
changes in the repository. So like Ross I would like the
functionality using the [hashcode] to be
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
On Thu, 22 Nov 2012 08:05:03 -0500
Richard Hipp d...@sqlite.org wrote:
(1) Just change the display format and do not worry about legacy
commit-comments. There are not that many check-in comments that look
different as text/x-fossil-wiki versus text/plain. If a few cases the
use of
2012/11/22 Richard Hipp d...@sqlite.org:
Fossil understands check-in comments and ticket text to be Wiki/HTML. Let's
say that the mimetype is text/x-fossil-wiki. This approach worked well
for us on CVSTrac (which was where many of the ideas in Fossil originated)
because it allowed hyperlinks
On 22 November 2012 14:05, Richard Hipp d...@sqlite.org wrote:
(3) Add a use text/plain mark to new check-in comments. Check-in comments
(and ticket text) are rendered in text/x-fossil-wiki by default but as
text/plain if they contain the new mark. There are a couple of possible
ways to add
On 22 November 2012 14:35, Jan Nijtmans jan.nijtm...@gmail.com wrote:
2012/11/22 Richard Hipp d...@sqlite.org:
Fossil understands check-in comments and ticket text to be Wiki/HTML. Let's
say that the mimetype is text/x-fossil-wiki. This approach worked well
for us on CVSTrac (which was where
On Thu, Nov 22, 2012 at 8:05 AM, Richard Hipp d...@sqlite.org wrote:
(1) Just change the display format and do not worry about legacy
commit-comments. There are not that many check-in comments that look
different as text/x-fossil-wiki versus text/plain. If a few cases the use
of text/plain
2012/11/22 Michal Suchanek hramr...@gmail.com:
On 22 November 2012 14:35, Jan Nijtmans jan.nijtm...@gmail.com wrote:
I think I would fix that in the comment preprocessor.
The major disadvantage is, of course, that this ugly mess will be
likely visible in the command line view of the commits
Comments and tickets are already text only. The point here is that in some
very specific contexts (timeline) and under demand (there is a setting),
they can be displayed as being wiki text. As this is optional, I do not see
the point to make it disappear.
However, with some very simple
This is great news!
Does this mean commit comments will respect embedded [CR+LF]
characters in the Timeline view?
Happy Thanksgiving all you American users :)
On Thu, Nov 22, 2012 at 11:23 AM, Ramon Ribó ram...@compassis.com wrote:
Comments and tickets are already text only. The point here is
13 matches
Mail list logo
