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 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 >

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

On 4/24/18, 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 think those are failed login attempts - where the

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 don't see anything

[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 th

Re: [fossil-users] question regarding fuel-scm maintenance / ownership

Am 27.12.2017 um 17:37 schrieb Olivier Mascia: > What Fossil version(s) does Fuel works with? I haven't seen a definitive list but I'm currently using the latest 2.4 (downloaded from fossil HP). So far I never had issues with whatever fossil version I was using since 1.34 (or so), so I never cared

Re: [fossil-users] question regarding fuel-scm maintenance / ownership

> Le 27 déc. 2017 à 17:25, Chris Drexler a écrit : > >> If you are unable to make contact, you might consider "forking" the project >> (under a new name) and maintaining it yourself. > > The project is currently available at > > https://server.ac-drexler.de/fossil/fuel > > if anyone is i

Re: [fossil-users] question regarding fuel-scm maintenance / ownership

Am 27.12.2017 um 04:39 schrieb Ron W: > If you are unable to make contact, you might consider "forking" the > project (under a new name) and maintaining it yourself. The project is currently available at     https://server.ac-drexler.de/fossil/fuel if anyone is interested. Chris ___

Re: [fossil-users] question regarding fuel-scm maintenance / ownership

Hi *, Am 27.12.2017 um 16:19 schrieb Warren Young: > On Dec 26, 2017, at 8:39 PM, Ron W wrote: >> If you are unable to make contact, you might consider "forking" the project >> (under a new name) and maintaining it yourself. > If it’s truly abandoned, you generally want to keep the name, unless

Re: [fossil-users] question regarding fuel-scm maintenance / ownership

On Dec 26, 2017, at 8:39 PM, Ron W wrote: > > If you are unable to make contact, you might consider "forking" the project > (under a new name) and maintaining it yourself. If it’s truly abandoned, you generally want to keep the name, unless it’s trademarked or “bad” in some way. A better reas

Re: [fossil-users] question regarding fuel-scm maintenance / ownership

On Tue, Dec 26, 2017 at 7:00 AM, wrote: > > Date: Mon, 25 Dec 2017 23:44:27 +0100 > From: Chris Drexler > Subject: [fossil-users] question regarding fuel-scm maintenance / > ownership > > Anyone here who knows any contact or has suggestions on what to do? I >

Re: [fossil-users] question regarding fuel-scm maintenance / ownership

To: Fossil SCM user's discussion Subject: Re: [fossil-users] question regarding fuel-scm maintenance / ownership Здравствуйте! Данный Вопрос не относится к программе лояльности. С Уважением, Программа лояльности «Семейная команда» -Original Message- From: fossil-users [mailto:f

Re: [fossil-users] question regarding fuel-scm maintenance / ownership

: fossil-us...@mailinglists.sqlite.org Subject: [fossil-users] question regarding fuel-scm maintenance / ownership Hi list, sorry for asking here but I could not find a better place (yet). I'm currently updating fuel (https://fuel-scm.org/)  to compile with that latest Qt version and switching

[fossil-users] question regarding fuel-scm maintenance / ownership

Hi list, sorry for asking here but I could not find a better place (yet). I'm currently updating fuel (https://fuel-scm.org/)  to compile with that latest Qt version and switching from it WebKit to WebEngine. I can't get a hold of "Kostas", the original author of fuel-scm to ask about how to proce

Re: [fossil-users] Question about the file formats.

On Dec 20, 2016 10:59 PM, "John Found" wrote: Well, the compression is the last thing I am talking about. It is important, but not essential. I am talking about several people working on one file and then fossil merging the changes automatically (of course if there is no conflicts in the edits).

Re: [fossil-users] Question about the file formats.

On Tue, Dec 20, 2016 at 08:48:27PM +0200, John Found wrote: > What makes the binary files different from the text files? The presence or > absence of > 0 bytes does not seems to make serious difference for processing by the same > algorithms. Many text formats allow merging changes from one vers

Re: [fossil-users] Question about the file formats.

On Dec 21, 2016 10:57 AM, "Warren Young" wrote: That is exactly what I’m talking about in my BMP vs PNG examples. If you wish to discuss a different file type than than bitmap graphics, give your own example. Until then, mine is the only concrete example we have available to discuss. Zip fil

Re: [fossil-users] Question about the file formats.

On Dec 20, 2016, at 10:59 PM, John Found wrote: > > Well, the compression is the last thing I am talking about. It is important, > but not essential. Then you’re missing the point I’m bringing up by talking about compression. If you check a file into Fossil that has a format where a change of

Re: [fossil-users] Question about the file formats.

Well, the compression is the last thing I am talking about. It is important, but not essential. I am talking about several people working on one file and then fossil merging the changes automatically (of course if there is no conflicts in the edits). On Tue, 20 Dec 2016 16:58:18 -0700 Warren Y

Re: [fossil-users] Question about the file formats.

On Dec 20, 2016, at 3:57 PM, Warren Young wrote: > >> What if I design some text file format (containing only ascii characters) and >> it can't be properly processed by fossil? > > Then you should post it as a replicable test case for our study. I decided to take up my own challenge. Consider:

Re: [fossil-users] Question about the file formats.

On Dec 20, 2016, at 12:35 PM, John Found wrote: > > Under "fossil algorithms" I mean two (in my understanding most important in > what is called "version control": diff algorithm and 3-way merge algorithm. When I said that Fossil can’t diff two binary files, I meant that it couldn’t display a

Re: [fossil-users] Question about the file formats.

Thus said John Found on Tue, 20 Dec 2016 21:35:44 +0200: > For example, I can't see what is the problem to make diff of binary > files. As a result one will have the bytes that have to be > inserted/deleted from the first file in order to turn it into the > second. (Or I am wro

Re: [fossil-users] Question about the file formats.

I am not talking about the fossil heuristics in detection of what file is binary and what file is text. Imagine all detection is switched off. Under "fossil algorithms" I mean two (in my understanding most important in what is called "version control": diff algorithm and 3-way merge algorithm.

Re: [fossil-users] Question about the file formats.

On Dec 20, 2016, at 11:48 AM, John Found wrote: > > I know that fossil (and most other version control systems) can handle > properly > only text source files. Says who? There are some features of Fossil that simply don’t work when given a binary file, like “fossil diff,” but if you think th

[fossil-users] Question about the file formats.

Hi. I know that fossil (and most other version control systems) can handle properly only text source files. I am designing a format for my application and have some questions about the files handling. They are very related, but in different form: What makes the binary files different from the

Re: [fossil-users] Question about MERGE

This is a surprisingly frequent need. Fossil is designed around a "get things right the first time" philosophy but real life is often not that crisp and clean. Being able to gracefully recover from mistakes and then get rid of the irrelevant leftover cruft would be a wonderful addition to fossil. I

Re: [fossil-users] Question about MERGE

On 10/28/15, Richard Hipp wrote: > On 10/28/15, to...@acm.org wrote: >> OK, but doesn't cherry-pick work the same as a MERGE but only for single >> version of the timeline? >> >> My intent was to get all changes from the branch (the whole history) but >> for >> > > Fossil does not currently suppo

Re: [fossil-users] Question about MERGE

On 10/28/15, to...@acm.org wrote: > OK, but doesn't cherry-pick work the same as a MERGE but only for single > version of the timeline? > > My intent was to get all changes from the branch (the whole history) but for > Fossil does not currently support the ability to merge some files but not othe

Re: [fossil-users] Question about MERGE

PM To: Fossil SCM user's discussion Subject: Re: [fossil-users] Question about MERGE On 10/28/15, to...@acm.org wrote: Today I tried something and got an unexpected result. So, I would like to know what the right way would have been. I created a new branch and made a whole bunch of changes

Re: [fossil-users] Question about MERGE

On 10/28/15, to...@acm.org wrote: > Today I tried something and got an unexpected result. So, I would like to > know what the right way would have been. > > I created a new branch and made a whole bunch of changes. Some of these > changes were tested, and so I decided to merge them in to the tru

[fossil-users] Question about MERGE

Today I tried something and got an unexpected result. So, I would like to know what the right way would have been. I created a new branch and made a whole bunch of changes. Some of these changes were tested, and so I decided to merge them in to the trunk. I did this by going to trunk, and the

[fossil-users] Question about fossil mv

Can someone explain me how exactly fossil manages moves? The actual problem is the following. Let's have a project, foo, with the following structure: foo/x/a.c foo/x/b.c foo/y/c.c foo/y/d.c The project sits on a central server. Two developers, Alice and Bob have their local clones on their mac

Re: [fossil-users] Question on moving a repository (possible bug?)

Hello Richard, [Issue with repository disappearing from the configuration database] Please try with trunk. Yes, this did resolve the issue! Thanks for the fast fix! ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-s

Re: [fossil-users] Question on moving a repository (possible bug?)

Please try with trunk. On Tue, Dec 16, 2014 at 6:19 PM, Robert Engelhardt < m...@robert-engelhardt.de> wrote: > > Hello, > > I discovered something strange when moving repositories (I wanted to > consolidate the location of some of mine). After some searching I came up > with three possibilities f

[fossil-users] Question on moving a repository (possible bug?)

Hello, I discovered something strange when moving repositories (I wanted to consolidate the location of some of mine). After some searching I came up with three possibilities for a repository relocation: 1) Simple moving the file and then updating the location both in the global configuratio

Re: [fossil-users] Question about command line matching branch creation

I just realized I never said: $ f version This is fossil version 1.30 [ffef4edceb] 2014-07-25 13:12:52 UTC * David J. Weller-Fahy [2014-08-02 22:42 -0500]: I've been trying to puzzle this out myself, but decided someone must know on the list. Assume I execute the following commands (with `a

[fossil-users] Question about command line matching branch creation

I've been trying to puzzle this out myself, but decided someone must know on the list. Assume I execute the following commands (with `alias f='fossil'`). #v+ alias f='fossil' f init ~/FOSSIL/1.fossil f open ~/FOSSIL/1.fossil touch 1 f add 1 f commit -m "1" mkdir 2 mkdir 3 cd 2 git init touch a

Re: [fossil-users] Question regarding ancestors and Q-card relations.

Thus said Richard Hipp on Wed, 04 Jun 2014 13:48:48 -0400: > No merge is perfect. Apparently you hit a bad case. But I do similar > things all the time on actual source code and rarely have problems. Ok, thanks. I just wanted to make sure I wasn't misunderstanding. I can offer up the repositor

Re: [fossil-users] Question regarding ancestors and Q-card relations.

On Wed, Jun 4, 2014 at 1:42 PM, Andy Bradford wrote: > Thus said Richard Hipp on Wed, 04 Jun 2014 07:47:43 -0400: > > > The merge logic in Fossil recognizes when the same exact change is > > merged more than once and avoids conflicts in that case. The Q-cards > > are not necessary for this.

Re: [fossil-users] Question regarding ancestors and Q-card relations.

Thus said Richard Hipp on Wed, 04 Jun 2014 07:47:43 -0400: > The merge logic in Fossil recognizes when the same exact change is > merged more than once and avoids conflicts in that case. The Q-cards > are not necessary for this. What am I doing wrong then? In this case, I did a cherr

Re: [fossil-users] Question regarding ancestors and Q-card relations.

On Wed, Jun 4, 2014 at 12:07 AM, Andy Bradford wrote: > Thus said Andy Bradford on Tue, 03 Jun 2014 21:59:21 -0600: > > > Does the Q-card here not imply any relation with c14a4a93d5a3 which will > > be picked up in trunk? > > It seems I did not understand this very well: > > A Q-card is simi

Re: [fossil-users] Question regarding ancestors and Q-card relations.

Thus said Andy Bradford on Tue, 03 Jun 2014 21:59:21 -0600: > Does the Q-card here not imply any relation with c14a4a93d5a3 which will > be picked up in trunk? It seems I did not understand this very well: A Q-card is similar to a P-card in that it defines a predecessor to the current

[fossil-users] Question regarding ancestors and Q-card relations.

Hello, While experimenting with --cherrypick I stumbled upon this situation: $ fossil merge trunk cannot find a common ancestor between the current checkout and trunk $ f stat | grep checkout checkout: 738e72e3d9cfe5568c94940c09ada1b78341ac68 2014-06-04 03:48:59 UTC $ fossil artifact 738e72e3

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

On 30 May 2014 08:24, Andy Bradford wrote: > Thus said Michai Ramakers on Thu, 29 May 2014 15:35:37 +0200: > >> Can anyone tell what happens under the hood here..? > > Bingo: > > http://www.fossil-scm.org/index.html/artifact/d1aef141c961172a1a32f619f339c641cdeaa674?ln=259,268 > > So it does indeed

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

On 30 May 2014 08:09, Andy Bradford wrote: > Thus said Michai Ramakers on Thu, 29 May 2014 15:35:37 +0200: > >> root@main:/tmp/ftmp# f sync f_f -R r_w >> Round-trips: 1 Artifacts sent: 0 received: 0 >> Error: Database error: unable to open database file: {CREATE TEMP >> TABLE onremote(rid INTEG

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

Thus said Michai Ramakers on Thu, 29 May 2014 15:35:37 +0200: > Can anyone tell what happens under the hood here..? Bingo: http://www.fossil-scm.org/index.html/artifact/d1aef141c961172a1a32f619f339c641cdeaa674?ln=259,268 So it does indeed call ``fossil http'' which will cause fossil to chroot a

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

Thus said Michai Ramakers on Thu, 29 May 2014 15:35:37 +0200: > root@main:/tmp/ftmp# f sync f_f -R r_w > Round-trips: 1 Artifacts sent: 0 received: 0 > Error: Database error: unable to open database file: {CREATE TEMP > TABLE onremote(rid INTEGER PRIMARY KEY);} > Round-trips: 1 Artifacts sent

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

Thus said Michai Ramakers on Thu, 29 May 2014 17:22:08 +0200: > Alright, thanks for looking into this (, all). Does this also explain > my last mail (in case one file is owned root.wheel, and the other file > and parent-dir are owned ftp.ftp, all works fine)? I may have mispoken earlier. Fossil

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

On Thu, May 29, 2014 at 5:22 PM, Michai Ramakers wrote: > Does this also explain my last mail (in case one file is owned > root.wheel, and the other file and parent-dir are owned ftp.ftp, all > works fine)? > Yes - because the file is owned by root, the "dropping of privileges" is actually a no-

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

Thus said Stephan Beal on Thu, 29 May 2014 17:12:35 +0200: > i = setgid(sStat.st_gid); > i = i || setuid(sStat.st_uid); > > sure enough. It switches back to the owning user/group of the repo. > > IMO, that's not a bug, just an unfortunate side effect of your setup. In fact, it's intende

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

Thus said Michai Ramakers on Thu, 29 May 2014 17:08:52 +0200: > In case both files as well as their parent-dir are owned ftp.ftp, both > syncs work fine. Sounds like a simple case of permissions problems to me. The user that is running the sync must have sufficient Unix filesystem privileges

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

On Thu, May 29, 2014 at 11:12 AM, Stephan Beal wrote: > On Thu, May 29, 2014 at 5:08 PM, Michai Ramakers > wrote: > >> In case both files as well as their parent-dir are owned ftp.ftp, both >> syncs work fine. >> > > If fossil drops permissions as Andy suggests (i'm still trying to find the > re

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

On 29 May 2014 17:12, Stephan Beal wrote: > On Thu, May 29, 2014 at 5:08 PM, Michai Ramakers > wrote: >> >> In case both files as well as their parent-dir are owned ftp.ftp, both >> syncs work fine. > > > If fossil drops permissions as Andy suggests (i'm still trying to find the > relevant code,

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

On 29 May 2014 17:08, Michai Ramakers wrote: > On 29 May 2014 16:36, Andy Bradford > wrote: >> Thus said Michai Ramakers on Thu, 29 May 2014 15:35:37 +0200: >> ... >> I could be wrong, but one thing you could try to verify is: >> >> chown ftp.ftp r_w >> f sync r_w -R f_f > > In case both files ar

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

On Thu, May 29, 2014 at 5:08 PM, Michai Ramakers wrote: > In case both files as well as their parent-dir are owned ftp.ftp, both > syncs work fine. > If fossil drops permissions as Andy suggests (i'm still trying to find the relevant code, but have no reason to believe he's wrong), then that's t

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

On 29 May 2014 16:36, Andy Bradford wrote: > Thus said Michai Ramakers on Thu, 29 May 2014 15:35:37 +0200: > >> root@main:/tmp/ftmp# ls -ld * . >> drwxr-xr-x 2 root wheel 512 May 29 15:32 . >> -rw-r--r-- 1 ftp ftp3435520 May 29 15:32 f_f >> -rw-r--r-- 1 root wheel 3592192 May 29 1

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

Thus said Michai Ramakers on Thu, 29 May 2014 15:35:37 +0200: > root@main:/tmp/ftmp# ls -ld * . > drwxr-xr-x 2 root wheel 512 May 29 15:32 . > -rw-r--r-- 1 ftp ftp3435520 May 29 15:32 f_f > -rw-r--r-- 1 root wheel 3592192 May 29 15:32 r_w > root@main:/tmp/ftmp# f sync r_w -R f_f

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

On Thu, May 29, 2014 at 4:11 PM, Richard Hipp wrote: > On Thu, May 29, 2014 at 9:57 AM, Stephan Beal > wrote: > >> (B) fossil always chroot's when run as root. >> > > That sounds right to me. Running Fossil as root causes a chroot and > /var/tmp does not exist inside the chroot jail. > In thi

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

On Thu, May 29, 2014 at 9:57 AM, Stephan Beal wrote: > (B) fossil always chroot's when run as root. > That sounds right to me. Running Fossil as root causes a chroot and /var/tmp does not exist inside the chroot jail. -- D. Richard Hipp d...@sqlite.org ___

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

On 29 May 2014 15:57, Stephan Beal wrote: > On Thu, May 29, 2014 at 3:35 PM, Michai Ramakers > wrote: >> >> In short, syncing with repo seems to work or not depending of >> perms/ownership of that repo: >> >> root@main:/tmp/ftmp# ls -ld * . >> root@main:/tmp/ftmp# f sync r_w -R f_f >> ... >> >> r

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

On Thu, May 29, 2014 at 3:35 PM, Michai Ramakers wrote: > In short, syncing with repo seems to work or not depending of > perms/ownership of that repo: > > root@main:/tmp/ftmp# ls -ld * . > root@main:/tmp/ftmp# f sync r_w -R f_f > ... root@main:/tmp/ftmp# f sync f_f -R r_w > Round-trips: 1 Art

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

On 29 May 2014 15:44, Richard Hipp wrote: > > On Thu, May 29, 2014 at 9:35 AM, Michai Ramakers > wrote: >> >> In short, syncing with repo seems to work or not depending of >> perms/ownership of that repo: >> >> root@main:/tmp/ftmp# ls -ld * . >> drwxr-xr-x 2 root wheel 512 May 29 15:32 . >

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

On Thu, May 29, 2014 at 9:35 AM, Michai Ramakers wrote: > Hello, > > ran to something I didn't understand just now, and turned out to be > (likely) a thing concerning permissions. > > In short, syncing with repo seems to work or not depending of > perms/ownership of that repo: > > root@main:/tmp/

[fossil-users] question about parms and ownership of repo vs current/parent dir

Hello, ran to something I didn't understand just now, and turned out to be (likely) a thing concerning permissions. In short, syncing with repo seems to work or not depending of perms/ownership of that repo: root@main:/tmp/ftmp# ls -ld * . drwxr-xr-x 2 root wheel 512 May 29 15:32 . -rw-r-

Re: [fossil-users] Question on config syncing

On Tue, Apr 29, 2014 at 11:03 AM, Stephan Beal wrote: > On Tue, Apr 29, 2014 at 7:44 PM, Andreas Kupries > wrote: >> >> Ok. Then the issue was me using an old version of fossil (1.21 of 2011). >> In the wake of the user/mtime issue I updated to the head, >> self-compiled (*) to see if that was th

Re: [fossil-users] Question on config syncing

On Tue, Apr 29, 2014 at 7:44 PM, Andreas Kupries wrote: > Ok. Then the issue was me using an old version of fossil (1.21 of 2011). > In the wake of the user/mtime issue I updated to the head, > self-compiled (*) to see if that was the issue. Which means that I > should be good on the rebuild front

Re: [fossil-users] Question on config syncing

On Tue, Apr 29, 2014 at 10:13 AM, Stephan Beal wrote: > On Tue, Apr 29, 2014 at 7:04 PM, Andreas Kupries > wrote: >> >> +1 from me. > > > If i hear no veto from Richard this evening i'll check it in. > >> >> Thinking of rebuilds, any chance of having the rebuild ignore tables >> whose names start

Re: [fossil-users] Question on config syncing

On Tue, Apr 29, 2014 at 7:04 PM, Andreas Kupries wrote: > +1 from me. > If i hear no veto from Richard this evening i'll check it in. > Thinking of rebuilds, any chance of having the rebuild ignore tables > whose names starts with "fx" (case-insensitive) ? > We added that late last Summer or F

Re: [fossil-users] Question on config syncing

Yes, that looks good to me. Thank you. On Tue, Apr 29, 2014 at 10:01 AM, Stephan Beal wrote: > On Tue, Apr 29, 2014 at 6:54 PM, Stephan Beal wrote: >> >> On Tue, Apr 29, 2014 at 6:52 PM, Andreas Kupries >> wrote: >>> >>> Now we "just" need some way for the fossil executable to auto-fix a >>> re

Re: [fossil-users] Question on config syncing

+1 from me. Thinking of rebuilds, any chance of having the rebuild ignore tables whose names starts with "fx" (case-insensitive) ? I currently work on a tool which stores some of its data in the repo db, in custom tables. A rebuild leaves these tables empty. On Tue, Apr 29, 2014 at 9:54 AM, St

Re: [fossil-users] Question on config syncing

On Tue, Apr 29, 2014 at 6:54 PM, Stephan Beal wrote: > On Tue, Apr 29, 2014 at 6:52 PM, Andreas Kupries > wrote: > >> Now we "just" need some way for the fossil executable to auto-fix a >> repository when it sees this type of damage. >> > > Any objections to me adding this to the rebuild bits: >

Re: [fossil-users] Question on config syncing

On Tue, Apr 29, 2014 at 6:52 PM, Andreas Kupries wrote: > Now we "just" need some way for the fossil executable to auto-fix a > repository when it sees this type of damage. > Any objections to me adding this to the rebuild bits: update user set mtime=strftime('%s','now') where mtime IS NULL ?

Re: [fossil-users] Question on config syncing

On Mon, Apr 28, 2014 at 6:55 PM, Andreas Kupries wrote: > On Mon, Apr 28, 2014 at 5:27 PM, Richard Hipp wrote: >> On Mon, Apr 28, 2014 at 8:23 PM, Richard Hipp wrote: >>> On Mon, Apr 28, 2014 at 5:09 PM, Andreas Kupries >>> wrote: > and lots of users are _not_ shown, especially not the new

Re: [fossil-users] Question on config syncing

On Mon, Apr 28, 2014 at 5:27 PM, Richard Hipp wrote: > On Mon, Apr 28, 2014 at 8:23 PM, Richard Hipp wrote: >> On Mon, Apr 28, 2014 at 5:09 PM, Andreas Kupries >> wrote: >>> and lots of users are _not_ shown, especially not the new "mi" entry. >> Fossil is running "SELECT * FROM user WHERE mti

Re: [fossil-users] Question on config syncing

On Mon, Apr 28, 2014 at 8:23 PM, Richard Hipp wrote: > > > > On Mon, Apr 28, 2014 at 5:09 PM, Andreas Kupries > wrote: > >> Logging in as admin to the Tcl repository and looking at the >> user list, i.e. >> http://core.tcl.tk/tcl/setup_ulist >> >> I see an entry for 'mi', id 92. >> >> Using

Re: [fossil-users] Question on config syncing

On Mon, Apr 28, 2014 at 5:09 PM, Andreas Kupries wrote: > Logging in as admin to the Tcl repository and looking at the > user list, i.e. > http://core.tcl.tk/tcl/setup_ulist > > I see an entry for 'mi', id 92. > > Using 'fossil config pull all' on the repository into my local copy, > then rebu

[fossil-users] Question on config syncing

Logging in as admin to the Tcl repository and looking at the user list, i.e. http://core.tcl.tk/tcl/setup_ulist I see an entry for 'mi', id 92. Using 'fossil config pull all' on the repository into my local copy, then rebuild'ing the local database, I lastly look at the local "user" table and

Re: [fossil-users] Question on repo size after repeated binary file commits?

On Sun, Dec 22, 2013 at 9:57 PM, wrote: > Really, I am only implying some minimal file statistic like 'DeltaSize(%)' > or somesuch to show the user it is in fact compared internally. The current > message contradicts what is in fact happening. Maybe change that message to > "Cannot visually displ

Re: [fossil-users] Question on repo size after repeated binary file commits?

Really, I am only implying some minimal file statistic like 'DeltaSize(%)' or somesuch to show the user it is in fact compared internally. The current message contradicts what is in fact happening. Maybe change that message to "Cannot visually display binary diffs. DeltaSize(%) = -10". On Sun, De

Re: [fossil-users] Question on repo size after repeated binary file commits?

On Sun, Dec 22, 2013 at 9:06 PM, wrote: > Thanks. I didn't know how binary was handled given the Timeline diff > response = "cannot compute difference between binary files". > That message is a bit misleading. It really means a "visual difference." There isn't a mechanism to show a textual diff

Re: [fossil-users] Question on repo size after repeated binary file commits?

Thanks. I didn't know how binary was handled given the Timeline diff response = "cannot compute difference between binary files". I think it would be cool if instead fossil listed some of the metrics used or determined in the binary delta operation. Thanks for Fossil! On Sun, Dec 22, 2013 at 2:5

Re: [fossil-users] Question on repo size after repeated binary file commits?

On Sun, Dec 22, 2013 at 8:44 PM, wrote: > Ah, is there a way to quantify the binary delta? > If I have a 1MB binary file and commit a 1 byte change, what is the size > of the computed binary delta? > Very, very small: Create two binaries with a one-byte difference: [stephan@host:~/cvs/fossil/l

Re: [fossil-users] Question on repo size after repeated binary file commits?

Ah, is there a way to quantify the binary delta? If I have a 1MB binary file and commit a 1 byte change, what is the size of the computed binary delta? You are correct of course, but I tend not to extend the spirit of fossil to binary files and images. It is their existence and not legacy that is

Re: [fossil-users] Question on repo size after repeated binary file commits?

On Sun, Dec 22, 2013 at 7:37 PM, wrote: > I am curious what is stored in the repo for each new commit that includes > a tiny change to a binary file. > Whether a dll or an image file, is fossil storing each binary file > compressed, uncompressed or some sort of delta? > Over time(6mo's to 1yr), I

Re: [fossil-users] Question on repo size after repeated binary file commits?

On Sun, Dec 22, 2013 at 1:37 PM, wrote: > I am curious what is stored in the repo for each new commit that includes > a tiny change to a binary file. > Whether a dll or an image file, is fossil storing each binary file > compressed, uncompressed or some sort of delta? > A binary delta. > Ove

[fossil-users] Question on repo size after repeated binary file commits?

I am curious what is stored in the repo for each new commit that includes a tiny change to a binary file. Whether a dll or an image file, is fossil storing each binary file compressed, uncompressed or some sort of delta? Over time(6mo's to 1yr), I would like to reduce my repo size by purging really

Re: [fossil-users] question about added, then deleted files and checkin

On 28 October 2013 15:10, Richard Hipp wrote: > >> What's the rationale for even mentioning the deleted file at all? Just >> for my info. > > Probably (I'm guessing) what you are seeing is some kind of bug that > prevents an unmanaged file that was previous added by not yet committed from > being

Re: [fossil-users] question about added, then deleted files and checkin

On Mon, Oct 28, 2013 at 10:04 AM, Michai Ramakers wrote: > Hello, > > when I do this: > > $ touch plop > $ fossil addremove > $ rm plop > $ fossil addremove > > ...I see in 'fossil status' and when doing 'fossil commit' one change, > namely the deleted file. When I commit, I see a resulting entry

[fossil-users] question about added, then deleted files and checkin

Hello, when I do this: $ touch plop $ fossil addremove $ rm plop $ fossil addremove ...I see in 'fossil status' and when doing 'fossil commit' one change, namely the deleted file. When I commit, I see a resulting entry in the webpage timeline with no changes. What's the rationale for even menti

Re: [fossil-users] Question about Source forge Fossil hosting

I mean you can login to your sourceforge account using the procedure described elsewhere in the thread. Then use wget to download the fossil sourcecode from fossil-scm.org. After unpacking the source code you can compile it on the sourceforge server. As a result you get a fossil executable which r

Re: [fossil-users] Question about Source forge Fossil hosting

Hello, what do you mean by : "can build fossil directly on the sourceforge machine" 1/ SSH access and download of checkins ? 2/ SSH access + ./configure directly with sourceforge... ?   Best Regards K. From : Mark Janssen Cc : jim Schimpf On Fri, Mar

Re: [fossil-users] Question about Source forge Fossil hosting

On Fri, Mar 29, 2013 at 7:49 PM, Jeff Rogers wrote: > Konstantin Khomoutov wrote: > >> On Fri, 29 Mar 2013 09:10:48 -0400 >> > > > 2. Obtain a fossil binary. Unfortunately the ones from the download page > on fossil-scm.org are built against a newer version of linux than SF's > servers and so wi

Re: [fossil-users] Question about Source forge Fossil hosting

Jan Nijtmans wrote: Jeff, this is a very useful recipe that should be documented in the fossil documentation somewhere! Tried it, and only found one obvious minor typo: >ssh -t myproject,myu...@shell.sourceforge.net crea

Re: [fossil-users] Question about Source forge Fossil hosting

On 04/05/2013 09:12 AM, Jan Nijtmans wrote: > Jeff, this is a very useful recipe that should be documented in > the fossil documentation somewhere! > > Tried it, and only found one obvious minor typo: >>ssh -t myproject,myu...@shell.sourceforge.net create > This should be: >>ssh -t myuser,myproj..

Re: [fossil-users] Question about Source forge Fossil hosting

Jeff, this is a very useful recipe that should be documented in the fossil documentation somewhere! Tried it, and only found one obvious minor typo: >ssh -t >myproject,myu...@shell.sourceforge.netcreate This should be: >ssh -t >myuser,myproj...@shell.sourceforge.netcreate A new "fosclipse" proj

Re: [fossil-users] Question about Source forge Fossil hosting

Konstantin Khomoutov wrote: On Fri, 29 Mar 2013 09:10:48 -0400 > I'd like to point out this is not at all a "source forge version". This is just a regular SF project created by someone -- see for yourself [1]. To my knowledge, SF does not provide Fossil hosting. SF doesn't provide it, but it

Re: [fossil-users] Question about Source forge Fossil hosting

On Fri, 29 Mar 2013 09:10:48 -0400 jim Schimpf wrote: > I have used Chiselapp for hosting some Fossil project but > just got a note that he is shutting down May first. So I decided to > try the source forge version (http://fossilrepos.sourceforge.net/) . I'd like to point out this is not

[fossil-users] Question about Source forge Fossil hosting

Hi, I have used Chiselapp for hosting some Fossil project but just got a note that he is shutting down May first. So I decided to try the source forge version (http://fossilrepos.sourceforge.net/) . Very easy to create a project but my previous experience with Chisel seems to not to a

Re: [fossil-users] Question about tags and autosync...

On Wed, Apr 25, 2012 at 07:00:08PM -0700, Matt Welland wrote: > On Wed, Apr 25, 2012 at 6:49 PM, Richard Hipp wrote: > > > > > > > On Wed, Apr 25, 2012 at 6:51 PM, Michael L. Barrow > > wrote: > > > >> Firstly, I'm running: > >>This is fossil version 1.21 [002580c50d] 2011-12-13 13:53:56 UTC

Re: [fossil-users] Question about tags and autosync...

On 4/25/12 6:49 PM, Richard Hipp wrote: What command did you use to create the tag? fossil tag add foo current I don't see any code associated with the "tag" command that will do an autosync. My suspicious is that the documentation you site above is incorrect and that "tag creation" should

Re: [fossil-users] Question about tags and autosync...

On Wed, Apr 25, 2012 at 6:49 PM, Richard Hipp wrote: > > > On Wed, Apr 25, 2012 at 6:51 PM, Michael L. Barrow wrote: > >> Firstly, I'm running: >>This is fossil version 1.21 [002580c50d] 2011-12-13 13:53:56 UTC >> >> Perhaps I'm confused, but the documentation for autosync being enabled >> sa

  1   2   >