Re: [fossil-users] Introducing Lagerstatte, an open-source hosting service for Fossil repositories

Vikrant Chaudhary wrote: On 30 March 2015 at 17:39, j. van den hoff veedeeh...@googlemail.com wrote: a marginal point, but in case you care: the german word for repository/deposit actually is Lagerstätte where the diacritical mark over the `a' really matters. but Lagerstatte sounds really

Re: [fossil-users] Spelling corrections for fossil-scm.org

jungle Boogie wrote: Hello All, I found the following spelling mistakes on the website. The misspelled word begins and ends in *. I don't know the difference between descendants vs. descendents Both are correct. Descendant seems to be more common than descendent, but it can be argued that

[fossil-users] getting rid of warning can't open /dev/null...

Apparently a change was made to Fossil in February to issue warnings about not being able to open /dev/null and /dev/urandom. I'm running a Fossil server from inetd under FreeBSD, and am getting these messages when I go into Administration. Since I can't do anything about the underlying reason

Re: [fossil-users] getting rid of warning can't open /dev/null...

On Tuesday, 26 May 2015 3:20 PM -0400, Richard Hipp wrote: On 5/26/15, Will Parsons varro@nodomain.invalid wrote: Apparently a change was made to Fossil in February to issue warnings about not being able to open /dev/null and /dev/urandom. I'm running a Fossil server from inetd under FreeBSD

Re: [fossil-users] user name question

Hi Stephan, Stephan Beal wrote: --===1226325735== Content-Type: multipart/alternative; boundary=f46d043894c5bea1ca04db4d5d30 --f46d043894c5bea1ca04db4d5d30 Content-Type: text/plain; charset=ISO-8859-1 On Sat, Apr 27, 2013 at 1:36 AM, Will Parsons varro@nodomain.invalidwrote

[fossil-users] local time is currently the same as UTC

Hi, I've set up (on FreeBSD) a fossil server using the inetd method. When looking at the timeline display I see the times displayed in UTC, and since I'd rather see local time, I tried to fix this using Timeline Display Preferences. However the Use UTC box is not checked, and in fact there is

Re: [fossil-users] local time is currently the same as UTC

Hi Maxim, Maxim Khitrov wrote: On Wed, May 1, 2013 at 7:21 PM, Will Parsons varro@nodomain.invalid wrote: Hi, I've set up (on FreeBSD) a fossil server using the inetd method. When looking at the timeline display I see the times displayed in UTC, and since I'd rather see local time, I tried

Re: [fossil-users] local time is currently the same as UTC

Hi Max, Thank you! Maxim Khitrov wrote: On Wed, May 1, 2013 at 8:08 PM, Will Parsons varro@nodomain.invalid wrote: Maxim Khitrov wrote: On Wed, May 1, 2013 at 7:21 PM, Will Parsons varro@nodomain.invalid wrote: Hi, I've set up (on FreeBSD) a fossil server using the inetd method. When

[fossil-users] how to edit All Tickets presentation

I've been using fossil for some of my private projects for a few months now, and at least on one of them there is no use for the subsystem field for tickets. I can see where to edit the schema to delete the field from the database, but for the life of me I can't figure out how to edit the All

Re: [fossil-users] how to edit All Tickets presentation

Ron Wilson wrote: On Thu, Oct 17, 2013 at 6:14 PM, Will Parsons varro@nodomain.invalidwrote: I can't figure out how to edit the All Tickets page to get rid of the subsystem column, and without that I will get an error when I display the page. You can edit the default default report from

Re: [fossil-users] how to edit All Tickets presentation

a summary report without it? Why? And how? On Thu, Oct 17, 2013 at 8:18 PM, Will Parsons varro@nodomain.invalidwrote: Ron Wilson wrote: On Thu, Oct 17, 2013 at 6:14 PM, Will Parsons varro@nodomain.invalid wrote: I can't figure out how to edit the All Tickets page to get rid

Re: [fossil-users] how to edit All Tickets presentation

Ron Wilson wrote: --===1527519250== I did not want to change the All Tickets report, so I created a new report, using the New report format link on the Tickets page. Then I removed the subsystem and comment fields from the SQL select statement, then saved it. Then I went back

[fossil-users] Making branches private and multiple private branches

I've been using Fossil as an SCM for one of my projects for about a year now. The program uses a GUI toolkit A, and since I wanted to experiment with alternative toolkits B C, some time ago I copied projname.fossil to projname-B.fossil and projname-C.fossil, created new branches B and C in the

Re: [fossil-users] Making branches private and multiple private branches

10, 2014 at 7:28 PM, Will Parsons varro@nodomain.invalidwrote: the main repository into the two secondary ones, but is it possible to then make branches B C private retroactively? The documentation only mentions creating a private branch with the first commit. If i'm not sorely mistaken, once

Re: [fossil-users] Making branches private and multiple private branches

Richard Hipp wrote: --===0261154002== Content-Type: multipart/alternative; boundary=047d7bea39f4fa833104f447520d --047d7bea39f4fa833104f447520d Content-Type: text/plain; charset=ISO-8859-1 On Mon, Mar 10, 2014 at 5:08 PM, Will Parsons varro@nodomain.invalidwrote: Richard Hipp

[fossil-users] anomaly using [g]diff

I recently revisited a working directory that I hadn't visited recently, so I wanted to review what the changes were, so here's what I found: - anukis% fossil stat repository: /home/william/FOSSIL/recepsum.fossil

Re: [fossil-users] anomaly using [g]diff

Jan Nijtmans wrote: Your .fossil file contains information on which files are locally changed. The vfile table rememberd rid's for each file which is in the current checkout. Those rid's are searched in the blob table in your recepsum.fossil database. My guess is that you re-cloned

Re: [fossil-users] Cannot determine user when using -A

Philip Bennefall wrote: I have been experimenting with Fossil for a few days now and am really liking it so far. I am in the process of switching all my old SVN repositories to Fossil and haven't had any trouble. However, I ran into an issue when creating a new repository today. To

Re: [fossil-users] Cannot determine user when using -A

Stephan Beal wrote: --===0473655165== Content-Type: multipart/alternative; boundary=047d7ba972dac592b704fb40f859 --047d7ba972dac592b704fb40f859 Content-Type: text/plain; charset=UTF-8 On Sat, Jun 7, 2014 at 5:18 PM, Will Parsons varro@nodomain.invalid wrote: Or you should

[fossil-users] how to push to chiselapp

I'm trying out chiselapp for the first time and running into difficulties. I managed to create an account for myself and upload an existing repo successfully, but I can't seem to figure out how to push changes to chiselapp. What I thought should work is: fossil push

Re: [fossil-users] how to push to chiselapp

Andy Bradford wrote: Thus said Will Parsons on Thu, 07 Aug 2014 00:53:53 -: Since I wasn't transmitting any sensitive data anyway, I answered yes, and then got: Error: not authorized to write Is there something wrong with the way I'm trying to authenticate? I see you used -B

Re: [fossil-users] how to push to chiselapp

Andy Bradford wrote: Thus said Will Parsons on Thu, 07 Aug 2014 00:53:53 -: fossil push https://chiselapp.com/user/uname/repository/reponame -B 'uname:passwd' By the way, if chiselapp does support HTTP_AUTH, then you might simply need to enable REMOTE_USER support in your

Re: [fossil-users] Elizabethan grammar [was: Fossil not updating to the true latest commit in branch]

Stephan Beal wrote: --===0605817196== Content-Type: multipart/alternative; boundary=047d7ba9828059d4a905022fb60a --047d7ba9828059d4a905022fb60a Content-Type: text/plain; charset=UTF-8 On Wed, Sep 3, 2014 at 11:05 PM, Ron W ronw.m...@gmail.com wrote: On Wed, Sep 3, 2014 at 3:39

Re: [fossil-users] Fossil not updating to the true latest commit in branch

Richard Hipp wrote: --===1631061293== Content-Type: multipart/alternative; boundary=047d7bb04ace7469e00502303533 --047d7bb04ace7469e00502303533 Content-Type: text/plain; charset=UTF-8 On Wed, Sep 3, 2014 at 5:13 PM, Stephan Beal sgb...@googlemail.com wrote: On Wed, Sep 3, 2014

Re: [fossil-users] Tags in comment document

Stephan Beal wrote: It's probably just an oversight. IIRC, the --tag option to commit was added relative recently (within the past year), and in my experience most people provide the message on the command line, so they never see that. i honestly can't remember the last time i let an scm

Re: [fossil-users] Tags in comment document

Stephan Beal wrote: --===1015663013== Content-Type: multipart/alternative; boundary=f46d04388df3ee3c0605027d793b --f46d04388df3ee3c0605027d793b Content-Type: text/plain; charset=UTF-8 On Sun, Sep 7, 2014 at 7:55 PM, Ron W ronw.m...@gmail.com wrote: It's still only a 1 line

[fossil-users] branch colour (and documentation typo)

I have a project in which I've created a number of branches (currently six). Perhaps by bad luck, three of the branches received quite similar varieties of blue/green as the background colour, and I'd like to have a better visual distinction among the branches. I see that one can use the

Re: [fossil-users] Proposed improvement to inheritedprivilegessubscripts.

Scott Robison wrote: --===0702352335== Content-Type: multipart/alternative; boundary=f46d044286d854da5a05042007d5 --f46d044286d854da5a05042007d5 Content-Type: text/plain; charset=UTF-8 On Sep 28, 2014 12:49 AM, Stephan Beal sgb...@googlemail.com wrote: Sidenote: i'm curious

Re: [fossil-users] Tab stop width

dave wrote: ... When Fossil displays a file in the repository, is it possible to tell it the width of the tab characters in the file? I could not find any setting to do that. Tab stops are hard-coded to every 8th character. There is no setting to change that. Would it

Re: [fossil-users] Tab stop width

Stephan Beal wrote: --===1471853227== Content-Type: multipart/alternative; boundary=089e0139fcda1d63f205044c8930 --089e0139fcda1d63f205044c8930 Content-Type: text/plain; charset=UTF-8 On Tue, Sep 30, 2014 at 6:26 PM, Ron W ronw.m...@gmail.com wrote: On the command line, I

[fossil-users] how to make link to zip file/tarball

I'd like to create a link to a zip file or tarball for downloading in the Fossil web interface for a application. The Fossil Web Interface page of the Fossil documentation suggests this is supported, but I can't find any further information on how to do this. Can someone describe this or point

Re: [fossil-users] how to make link to zip file/tarball

Stephan Beal wrote: --===0338390041== Content-Type: multipart/alternative; boundary=047d7bd9201abd3d160508510448 --047d7bd9201abd3d160508510448 Content-Type: text/plain; charset=UTF-8 On Thu, Nov 20, 2014 at 10:25 PM, Will Parsons varro@nodomain.invalid wrote: I'd like

Re: [fossil-users] how to make link to zip file/tarball

Stephan Beal wrote: --===1833591206== Content-Type: multipart/alternative; boundary=047d7bfced30f661db0508511b3c --047d7bfced30f661db0508511b3c Content-Type: text/plain; charset=UTF-8 On Thu, Nov 20, 2014 at 10:29 PM, Stephan Beal sgb...@googlemail.com wrote: And see:

Re: [fossil-users] How to force text for all files?

to...@acm.org wrote: This is a multi-part message in MIME format. --===0379594130== Content-Type: multipart/alternative; boundary==_NextPart_000_001C_01D01261.2A93EE90 This is a multi-part message in MIME format. --=_NextPart_000_001C_01D01261.2A93EE90

Re: [fossil-users] How to force text for all files?

to...@acm.org wrote: -Original Message- From: Will Parsons And how could one possibly distinguish a file containing all 256 byte bit patterns from a binary file? That's the point, in effect you can't. It's up to you to decide how to interpret a file. Referring to all 256 ASCII

[fossil-users] documentation bug

In the help test for push, the description of the -R option reads: -R|--repository REPO Repository to pull into whereas I think it should read "repository to push from" or similar. -- Will ___ fossil-users mailing list

Re: [fossil-users] Download v1.36 Linux x86 tar.gz actually contains 64bit binary

On Tuesday, 15 Nov 2016 5:46 AM -0500, Joerg Sonnenberger wrote: > Dear "K. Fossil user", > it's been said before. Please keep your aggressive attitude and > platitudes to yourself. You are just annoying and distracting people. It should be pretty clear by now that "K. Fossil user" is a troll.

Re: [fossil-users] EXECUTABLE, and not really being added to updated repo

On Tuesday, 6 Dec 2016 5:46 PM -0500, bch wrote: > I've got a collection of files who's apparently only change is the > EXECUTABLE bit set, but after a commit, they're still showing up in "f > chan"; I retried w/ a --sha1sum switch; still listed as changed > (despite the new commit showing up in

[fossil-users] download compressed tarball from repository

In one of my projects using Fossil, I wish to provide the software both as a zip file and a compressed tarball. In fact, I thought I'd already done this and it was working by providing the following links: Current trunk (zip file) Current trunk (compressed tar file) On recently trying though,

Re: [fossil-users] download compressed tarball from repository

Richard Hipp wrote: > On 12/10/16, Will Parsons <wbp@nodomain.invalid> wrote: >> In one of my projects using Fossil, I wish to provide the software both as a >> zip file and a compressed tarball. In fact, I thought I'd already done this >> and it was working by pr

Re: [fossil-users] spam after posting to the list

On Sunday, 5 Mar 2017 7:59 AM -0500, Saša Janiška wrote: > Hello, > > my last post to the list has triggered 7 *different* spam messages to my > INBOX from the *same* author, so wonder if there is something which can > be done against it, iow. I wonder if the situation is same whether one >

Re: [fossil-users] feature request: diff -tk: 'q' to quit

On Saturday, 11 Nov 2017 7:08 PM -0500, Stephan Beal wrote: > --===3478356516174635687== > Content-Type: multipart/alternative; boundary="94eb2c1cc16658e44a055dbdf4c0" > > --94eb2c1cc16658e44a055dbdf4c0 > Content-Type: text/plain; charset="UTF-8" > > Lol - i never even noticed that

[fossil-users] How to link to licence file in fossil wiki

I've just added a plain-text LICENCE file to one of my projects that uses Fossil, and I'd like to add a link to it from the project homepage that will display the file's contents when the link is followed. I thought the obvious way to do that would be add something like this to the home page:

Re: [fossil-users] How to link to licence file in fossil wiki

On Friday, 11 May 2018 10:43 AM -0400, Warren Young wrote: > On May 11, 2018, at 8:09 AM, Richard Hipp wrote: >> >> License > > If that works, then I’d strongly suggest text/plain instead. You don’t want > Fossil to tell the browser that it should try interpreting

Re: [fossil-users] This mailing list is now deprecated

On Wednesday, 8 Aug 2018 8:40 AM -0400, Richard Hipp wrote: > The new "forum" feature of Fossil is now live on the self-hosting website: > > https://fossil-scm.org/forum > > The forum feature is intended as a replacement for mailing lists like > this one. Though still very "beta", I believe

Re: [fossil-users] Feature slideshow on fossil homepage

On Monday, 9 Jul 2018 12:06 PM -0400, mario wrote: > As followup to last month` Show time.. discussion: > > → http://fossilslideshow.tmp.include-once.org/ > > (Take in mind this ain't a mockup yet; just as example.) > Discussion >== > > Is this something the Fossil homepage should

[fossil-users] question about background colour in Fossil/Chiselapp access log

I use Chiselapp to host several of my fossil repositories, and I'm puzzled to see that in the Access Log of one of my repositories on Chisel that some (but only some) of the entries have a pink background. I don't see anything obviously distinctive between the entries with a pink background and

Re: [fossil-users] question about background colour in Fossil/Chiselapp access log

On Tuesday, 24 Apr 2018 9:28 PM -0400, Richard Hipp wrote: > On 4/24/18, Will Parsons <varro@nodomain.invalid> wrote: >> I use Chiselapp to host several of my fossil repositories, and I'm >> puzzled to see that in the Access Log of one of my repositories on >> Chis

Re: [fossil-users] question about background colour in Fossil/Chiselapp access log

On Tuesday, 24 Apr 2018 9:03 PM -0400, Will Parsons wrote: > I use Chiselapp to host several of my fossil repositories, and I'm > puzzled to see that in the Access Log of one of my repositories on > Chisel that some (but only some) of the entries have a pink > background. > > I