On Mon, May 27, 2013 at 2:46 AM, Richard Hipp <d...@sqlite.org> wrote: > > On Sun, May 26, 2013 at 8:39 PM, Richard Collins <richa...@richardc.net> > wrote: >> >> I'm looking at switching a git repository to fossil. >> >> I've done an export and import and found that fossil is not showing the >> newlines from the commit messages. >> >> e.g. the commit message >> >> Fix slow PDF thumbnail generation >> >> Squashed commit of the following: >> commit 350fe7521e79a914a54ff384b6ca02a66d5ba136 >> Author: Richard Collins >> ... >> ... >> >> Shows up in the fossil web UI as: >> >> Fix slow PDF thumbnail generation Squashed commit of the following: commit >> 350fe7521e79a914a54ff384b6ca02a66d5ba136 Author: Richard Collins ... >> >> >> Which is not that great for long commit messages. I don't know if newlines >> are dropped in the import, or if the UI does not htmlize the newlines. Is >> there a way to get fossil to import/display the newlines? > > > Under the Admin/Timeline menu you can select "Plaintext comments on > timeline", among other options.
The problem is that the commit message is not shown within <pre> tags, so even if line feeds are preserved, the browser will discard them as whitespace. In my case that's not really an issue (for migrated Mercurial repositories) but I wonder if introducing markup in commit messages is a recommended practice around here. Cheers. P.S: Apparently, the command line timeline also joins all the message into a single line. I still have to look through the code to see if it's done at commit/import time or just at rendering. -- Isaac Jurado "The noblest pleasure is the joy of understanding" Leonardo da Vinci _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
