Re: [fossil-users] GitHub question. Was: Git-v-Fossil.

On Saturday, March 14, 2015, Richard Hipp wrote: > On 3/14/15, Ron W > wrote: > > > > The key difference is that, in git, the puller can force the in coming > > commits to be remapped into branches of their own. That is, I could > commit > > my changes to "trunk" in my clone, then when the other

Re: [fossil-users] fossil ui not working with recent chrome browser

Probably nothing to do with Fossil but that's an interesting 'feature', reminds me somehow of features I had some times ago with SWF rendering. Maybe I get an idea when I see the page source Opera or Chrome claim to have received when they display only half of the new ticket page... Additiona

Re: [fossil-users] fossil ui not working with recent chrome browser

Am 15.03.2015 um 01:49 schrieb Tontyna: > Am 15.03.2015 um 00:30 schrieb a...@gmx-topmail.de: >> yes, I just did that (Fossil version [6c40678e91] 2015-03-14 13:20:34) >> and still see the same problem: only part of the html-code is rendered >> and when I look at the page source that chrome claims

Re: [fossil-users] fossil ui not working with recent chrome browser

Am 15.03.2015 um 00:31 schrieb Richard Hipp: > On 3/14/15, a...@gmx-topmail.de wrote: >> Am 14.03.2015 um 16:30 schrieb Richard Hipp: >>> On 3/14/15, a...@gmx-topmail.de wrote: I am having problems to access my local fossil repositories with a recent versions of chrome, it looks li

Re: [fossil-users] How to change background color dynamically?

Thanks! That worked but why not with other globals? Are they not available with the default fossil.exe? I initially tried this TH1 in the CSS but it failed and assumed it was not allowed? /* This fails */ if { [ string last "c" $project_name ] == [ string length $project_name ] - 1 } { puts

Re: [fossil-users] Fossil version 1.32

Thus said bch on Sun, 15 Mar 2015 01:05:42 -0700: > Has the Ryerson Bug be characterised? Yes. Basically, versions of Fossil 1.27 and older, assumed that the first rid in the blob table would always be a checkin. This was true because the first thing fossil new did was to create a bogus check

Re: [fossil-users] New skin: Blitz

Hi Sean, Normalize gets you to a level playing field across browsers but it is a starting point for creating a consistently operating CSS theme - it's not an endpoint. If you want a modern-looking CSS toolkit and don't mind looking like almost everyone else, then Twitter Bootstrap is a great choi

Re: [fossil-users] Fossil XML SVN like export

2015-03-15 11:37 GMT+01:00 Kai Lauterbach : > Hi, > > is there away to export fossil's timeline like the log output in subversion? > > SVN export example: > > svn log -r 1:HEAD --xml --verbose --quiet > > if you have the json option enabled you do have: fossil json timeline checkin regards, Bapt

[fossil-users] Fossil XML SVN like export

Hi, is there away to export fossil's timeline like the log output in subversion? SVN export example: svn log -r 1:HEAD --xml --verbose --quiet Thanks! ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi

Re: [fossil-users] Fossil version 1.32

Am 15.03.2015 um 09:46 schrieb Baruch Burstein: Can we still have the changelog of the older versions on the download page, even without the links? And/or a link to "older versions" like on ___ fossil-

Re: [fossil-users] How to change background color dynamically?

Sat, 14 Mar 2015 20:06:06 -0400 : > ... > clones. I understand TH1 only works inside the header/footer > sections, so is it possible to maybe change just their backgrounds? > Currently, CSS sets my entire background color. You can also use TH1 for the stylesheet (Admin > CSS). It's a proper templ

Re: [fossil-users] Fossil version 1.32

On Sat, Mar 14, 2015 at 4:30 PM, Richard Hipp wrote: > Fossil version 1.32 is now available on the download page: > https://www.fossil-scm.org/download.html > > The new builds all use version numbers in their names instead of dates. > > All previous builds have been removed from the download page

Re: [fossil-users] Fossil version 1.32

Has the Ryerson Bug be characterised? Obviously it was confusing, annoying and unintended, but did it turn out to be data losing and/or uncorrectable? Regards -bch On Mar 14, 2015 7:24 PM, "Richard Hipp" wrote: > On 3/14/15, James Turner wrote: > > It appears the actual tarballs were also rem

Re: [fossil-users] Google code shutting down

On 14/03/15 22:03, David Mason wrote: Thank you Graeme for your thought-provoking post. It seems most challenges and rebuttals have played out. Thank you. Yes, I think the discussion is nearly done. If anyone was mining this thread for ways to improve fossil, I think they'd see 2 things: 1