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 builds just ignore the
additional fields? Then there is no problem.
This reminds me of another (maybe can of worms) idea: Why not let
users add J fields per repository, they could be used to store file
permissions etc, but are the responsibility of the repository, not the
fossil executable.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
