On Thu, 22 Nov, Jan Nijtmans wrote:
Stefan, could you try out [e6a1910fa8]?
This sounds very cool. :-)
However I still get:
$ ~/tmp/fossil addremove
[...]
/home/bellonsn/tmp/fossil: filename contains illegal characters: str\i\ng.h
This is with:
$ ~/tmp/fossil version
This is fossil version
2012/11/22 Stefan Bellon sbel...@sbellon.de:
On Thu, 22 Nov, Jan Nijtmans wrote:
Stefan, could you try out [e6a1910fa8]?
This sounds very cool. :-)
However I still get:
$ ~/tmp/fossil addremove
[...]
/home/bellonsn/tmp/fossil: filename contains illegal characters: str\i\ng.h
...
Am I
I downloaded and built fossil (v 1.24) from source for a QNAP TS419L nas, so
that I could access repositories over the network. Although it mostly works,
there is a very minor problem in that the footer of generated web pages say:
This page was generated in about
ERROR: no such command: utime
On 22 Nov 2012, at 11:33, Julian wrote:
I downloaded and built fossil (v 1.24) from source for a QNAP TS419L nas, so
that I could access repositories over the network.
Oops, minor typo there - I meant a QNAP 469L, which uses an Intel Atom
processor, not one of the ones with an Arm
On Thu, Nov 22, 2012 at 6:33 AM, Julian j...@ptolserv.com wrote:
I downloaded and built fossil (v 1.24) from source for a QNAP TS419L nas,
so that I could access repositories over the network. Although it mostly
works, there is a very minor problem in that the footer of generated web
pages
On Wed, 21 Nov 2012 20:51:09 -0800, E. Timothy Uy
t...@loqu8.com wrote:
ExamDiff Pro. http://www.prestosoft.com/edp_examdiffpro.asp
On Wed, Nov 21, 2012 at 7:47 PM, Tomek Kott tkott.li...@outlook.com wrote:
fwiw I've used kdiff3 (http://kdiff3.sourceforge.net/) on windows with
good success.
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 to other check-ins, tickets,
wiki, etc to be
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
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
used with commit...
fossil commit -m Some commit -tag some tags
...
On 22 Nov 2012, at 12:30, Richard Hipp wrote:
The utime command for the embedded TH1 scripting language was added after
the 1.24 release. The script used to generate the footer on Fossil itself is
non-standard and uses that command, however. The utime command should not
show up in new
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
NetSurf [0] is probably a lesser known browser, but I run it on my
Lemote Yeeloong, which is mips based and doesn't support larger browsers
like Firefox under OpenBSD. It might be nice to have it added. Thanks.
[0] http://www.netsurf-browser.org/
--
James Turner
ja...@calminferno.net
Index:
18 matches
Mail list logo
