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

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

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

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

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

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

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

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

On Tue, Dec 26, 2017 at 7:00 AM, <fossil-users-requ...@lists.fossil-scm.org> wrote: > > Date: Mon, 25 Dec 2017 23:44:27 +0100 > From: Chris Drexler <ckolum...@ac-drexler.de> > Subject: [fossil-users] question regarding fuel-scm maintenance / > ownership &g

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

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

To: 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 from

[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

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

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

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

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

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

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

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

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

[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

[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

Re: [fossil-users] Question about MERGE

To: Fossil SCM user's discussion Subject: Re: [fossil-users] Question about MERGE On 10/28/15, to...@acm.org <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

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

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

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

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.

[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

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

[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

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 for 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 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 dave+lists.fossil-us...@caterva.org [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

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

On Wed, Jun 4, 2014 at 12:07 AM, Andy Bradford amb-fos...@bradfords.org 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

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

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

On Wed, Jun 4, 2014 at 1:42 PM, Andy Bradford amb-fos...@bradfords.org 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

[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

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

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

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

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

On 30 May 2014 08:09, Andy Bradford amb-sendok-1404022150.hdbpagcekdcgljghk...@bradfords.org 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

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

On 30 May 2014 08:24, Andy Bradford amb-sendok-1404023072.eeipjlgjbincchjbb...@bradfords.org wrote: Thus said Michai Ramakers on Thu, 29 May 2014 15:35:37 +0200: Can anyone tell what happens under the hood here..? Bingo:

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

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 m.ramak...@gmail.com 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:

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

On 29 May 2014 15:44, Richard Hipp d...@sqlite.org wrote: On Thu, May 29, 2014 at 9:35 AM, Michai Ramakers m.ramak...@gmail.com 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

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 m.ramak...@gmail.com 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

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

On 29 May 2014 15:57, Stephan Beal sgb...@googlemail.com wrote: On Thu, May 29, 2014 at 3:35 PM, Michai Ramakers m.ramak...@gmail.com 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

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 sgb...@googlemail.com 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 Thu, May 29, 2014 at 4:11 PM, Richard Hipp d...@sqlite.org wrote: On Thu, May 29, 2014 at 9:57 AM, Stephan Beal sgb...@googlemail.com 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

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 When

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

On 29 May 2014 16:36, Andy Bradford amb-sendok-1403966191.gpijlhaollnogheom...@bradfords.org 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

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 m.ramak...@gmail.com 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

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

On 29 May 2014 17:08, Michai Ramakers m.ramak...@gmail.com wrote: On 29 May 2014 16:36, Andy Bradford amb-sendok-1403966191.gpijlhaollnogheom...@bradfords.org 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:

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

On 29 May 2014 17:12, Stephan Beal sgb...@googlemail.com wrote: On Thu, May 29, 2014 at 5:08 PM, Michai Ramakers m.ramak...@gmail.com 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

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 sgb...@googlemail.com wrote: On Thu, May 29, 2014 at 5:08 PM, Michai Ramakers m.ramak...@gmail.com 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

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

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 intended

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 m.ramak...@gmail.com 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

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 on config syncing

On Mon, Apr 28, 2014 at 6:55 PM, Andreas Kupries andre...@activestate.com wrote: On Mon, Apr 28, 2014 at 5:27 PM, Richard Hipp d...@sqlite.org wrote: On Mon, Apr 28, 2014 at 8:23 PM, Richard Hipp d...@sqlite.org wrote: On Mon, Apr 28, 2014 at 5:09 PM, Andreas Kupries andre...@activestate.com

Re: [fossil-users] Question on config syncing

On Tue, Apr 29, 2014 at 6:52 PM, Andreas Kupries andre...@activestate.comwrote: 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')

Re: [fossil-users] Question on config syncing

On Tue, Apr 29, 2014 at 6:54 PM, Stephan Beal sgb...@googlemail.com wrote: On Tue, Apr 29, 2014 at 6:52 PM, Andreas Kupries andre...@activestate.com 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

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,

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 sgb...@googlemail.com wrote: On Tue, Apr 29, 2014 at 6:54 PM, Stephan Beal sgb...@googlemail.com wrote: On Tue, Apr 29, 2014 at 6:52 PM, Andreas Kupries andre...@activestate.com wrote: Now we just need

Re: [fossil-users] Question on config syncing

On Tue, Apr 29, 2014 at 7:04 PM, Andreas Kupries andre...@activestate.comwrote: +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

Re: [fossil-users] Question on config syncing

On Tue, Apr 29, 2014 at 10:13 AM, Stephan Beal sgb...@googlemail.com wrote: On Tue, Apr 29, 2014 at 7:04 PM, Andreas Kupries andre...@activestate.com 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

Re: [fossil-users] Question on config syncing

On Tue, Apr 29, 2014 at 7:44 PM, Andreas Kupries andre...@activestate.comwrote: 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

Re: [fossil-users] Question on config syncing

On Tue, Apr 29, 2014 at 11:03 AM, Stephan Beal sgb...@googlemail.com wrote: On Tue, Apr 29, 2014 at 7:44 PM, Andreas Kupries andre...@activestate.com 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,

[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 config syncing

On Mon, Apr 28, 2014 at 5:09 PM, Andreas Kupries andre...@activestate.comwrote: 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

Re: [fossil-users] Question on config syncing

On Mon, Apr 28, 2014 at 8:23 PM, Richard Hipp d...@sqlite.org wrote: On Mon, Apr 28, 2014 at 5:09 PM, Andreas Kupries andre...@activestate.com 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

Re: [fossil-users] Question on config syncing

On Mon, Apr 28, 2014 at 5:27 PM, Richard Hipp d...@sqlite.org wrote: On Mon, Apr 28, 2014 at 8:23 PM, Richard Hipp d...@sqlite.org wrote: On Mon, Apr 28, 2014 at 5:09 PM, Andreas Kupries andre...@activestate.com wrote: and lots of users are _not_ shown, especially not the new mi entry.

[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

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

On Sun, Dec 22, 2013 at 7:37 PM, sky5w...@gmail.com 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

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 8:44 PM, sky5w...@gmail.com 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:

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

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

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

On Sun, Dec 22, 2013 at 9:57 PM, sky5w...@gmail.com 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

[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

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

On Mon, Oct 28, 2013 at 10:04 AM, Michai Ramakers m.ramak...@gmail.comwrote: 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

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

On 28 October 2013 15:10, Richard Hipp d...@sqlite.org 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

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 mailto:myu...@shell.sourceforge.netmailto:myu...@shell.sourceforge.net create

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

[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

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

On Fri, 29 Mar 2013 09:10:48 -0400 jim Schimpf jim.schi...@gmail.com 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

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

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 d...@sqlite.org wrote: On Wed, Apr 25, 2012 at 6:51 PM, Michael L. Barrow mlbar...@barrow.mewrote: Firstly, I'm running: This is fossil version 1.21 [002580c50d]

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

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 says: autosync If enabled, automatically pull prior to commit or update and automatically push after

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

On Wed, Apr 25, 2012 at 6:51 PM, Michael L. Barrow mlbar...@barrow.mewrote: 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 says: autosync If enabled, automatically

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

On Wed, Apr 25, 2012 at 6:49 PM, Richard Hipp d...@sqlite.org wrote: On Wed, Apr 25, 2012 at 6:51 PM, Michael L. Barrow mlbar...@barrow.mewrote: 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

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 be

[fossil-users] question about makemake.tcl and non-Unix platforms

Hi, all, i've added a couple files to my local json fork of fossil and i've got a question: the new files are in makemake.tcl, and they're built fine for Make-based builds on Unix, but is there anything special i need to be doing to get them added to the Windows/etc builds? -- - stephan

Re: [fossil-users] question

On Thu, Jul 21, 2011 at 4:23 AM, Rene renew...@xs4all.nl wrote: On Wed, 20 Jul 2011 20:10:45 -0400, Richard Hipp wrote: On Wed, Jul 20, 2011 at 5:15 PM, Zhang, Jenny wrote: HI, I WOULD LIKE TO KNOW IF FOSSIL CAN HANDEL VERSION CONTROL FOR BINARY FILES? Yes. For example I

[fossil-users] Question on short-lived branches in fossil

So I created the 'autosetup' branch and added a commit which drh then merged to trunk. Is that branch now defunct? If I want to propose some more, related changes, do I create a new branch, say autosetup2, or do I continue or resurrect the autosetup branch? If so, how? Thanks, Steve -- µWeb:

Re: [fossil-users] Question on short-lived branches in fossil

On Fri, Jul 22, 2011 at 7:57 AM, Steve Bennett ste...@workware.net.auwrote: So I created the 'autosetup' branch and added a commit which drh then merged to trunk. Is that branch now defunct? If I want to propose some more, related changes, do I create a new branch, say autosetup2, or do I

Re: [fossil-users] Question on short-lived branches in fossil

On Jul 22, 2011, at 13:57 , Steve Bennett wrote: So I created the 'autosetup' branch and added a commit which drh then merged to trunk. Is that branch now defunct? If your changes are well integrated into trunk, and you're not continuing development in isolation from trunk, you should

Re: [fossil-users] Question on short-lived branches in fossil

On Jul 22, 2011, at 14:46 , Richard Hipp wrote: fossil commit --branch autosetup --bgcolor '#91d680' The --bgcolor on the last commit is optional. But it is nice to have color on branches. If you forget it, it can be added later using the Edit feature of the UI. (That's how I added

  1   2   >