Re: [fossil-users] Unversioned files.

ld be possible to estimate where Fossil might > be a reasonable solution and where some other approach is needed. > I may not be understanding you, but from my point of view, it already does what you want by supporting versioned files that you simply never

Re: [fossil-users] Unversioned files.

On Sun, Sep 11, 2016 at 3:27 PM, Adam Jensen <han...@riseup.net> wrote: > On 09/11/2016 04:42 PM, Scott Robison wrote: > > I may not be understanding you, but from my point of view, it already > > does what you want by supporting versioned files that you simply never > &g

Re: [fossil-users] Files named "AUX" on Windows

lly looks bad to someone for not creating what appear to be ordinary file names. If we do support it, Fossil potentially looks bad for creating files or directories that other processes can't interact with normally. I wouldn't mind taking a stab at it if enough people think it is worthwhile, but

Re: [fossil-users] Files named "AUX" on Windows

in a file name is the forward slash. > > ...and NUL, I beleive. > Not to be confused with the DOS/Windows NUL device. :) -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

lf in the foot. :) > Hold on, you mean fossil expects me to read the output to understand the current state and status of commands issued? That's pretty user unfriendly... -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil

Re: [fossil-users] features I'd like to have in fossil

> If you color lines by meaing, it is easier to understand: Unless you're color blind, in which case it might be impossible to understand. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] on sha1 as a hash

more likely that someone will compromise a server with a weak password and completely replace the good repo with a bad repo, or just host a fork that looks legit and get people to pull from that instead. -- Scott Robison ___ fossil-users mailing list

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

On Nov 11, 2016 5:28 PM, "K. Fossil user" wrote: > > Ah you don't understand again what I've said ... > > 1/ Fossil and SQLite work together, and to be clear, the same guy work for both projects. > I was even told that the AIM of Fossil is to help SQLite. > Do you

Re: [fossil-users] disabled due to excessive bounces (again?)

On Oct 16, 2016 6:35 PM, "K. Fossil user" wrote: > > I am angry because Fossil knows nothing about marketing which is bad for any project... If I may paraphrase, Fossil's benevolent dictator has stated many times in the past that the One True Purpose (TM) of

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] [PROPOSED FEATURE] Fossil commands output sent through a pager

I don't know about what commands to paginate by default, but no to versionable settings for this. Don't want to force this on others. On Mar 23, 2017 4:08 PM, "Christophe Gouiran" wrote: > Good morning, > > I would like to implement the feature given in the title. > I'm

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

On Mar 26, 2017 11:25 AM, "Christophe Gouiran" wrote: Please find as attached file another patch which: 1. First test for a real terminal before spawning the pager command. 2. No more paginate json command. I see that most of you complain about this proposed

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

On Mar 26, 2017 7:13 AM, "Christophe Gouiran" wrote: Hi all, First of all many thanks for all your feedback. I come back to you with an implemented solution. After many thinking, for me not all commands need to send their outputs to a pager. Only ones which may output

Re: [fossil-users] Couple of beginner questions

sibly need. You have my word on it!" True story. ;) -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] update Fossil performance chart?

On Wed, Mar 29, 2017 at 9:46 AM, jungle Boogie wrote: > On 28 February 2017 at 08:04, jungle Boogie wrote: >> Hi All, >> >> This is most likely a request only Dr. Hipp can fulfill has he has >> access to all the databases. >> >> Is it possible

Re: [fossil-users] Fossil interprets plain-text file as a binary file

On Mar 27, 2017 6:44 PM, "Byron Sanchez" wrote: Recently, however, fossil has started interpreting one of these org-mode files as a binary file. Now, fossil prompts with it's binary-file warning each time I update the file. In addition, this file can no longer be diffed in the

Re: [fossil-users] Is Fossil Hash-collision proof?

On Mar 21, 2017 11:04 PM, "Martin Vahi" wrote: I haven't encountered any collisions yet, but I was wondering, what will happen, if 2 different files that have the same size, same timestamps, different bitstreams, but the same hash (regardless of hash algorithm) were to

Re: [fossil-users] Issue with ignore-glob

On Mon, Apr 10, 2017 at 1:58 PM, Thomas <tho...@dateiliste.com> wrote: > On 2017-04-10 20:34, Scott Robison wrote: >> >> On Mon, Apr 10, 2017 at 1:05 PM, Thomas <tho...@dateiliste.com> wrote: >>> >>> On 2017-04-10 20:00, Scott Robison wrote: >&g

Re: [fossil-users] Issue with ignore-glob

On Mon, Apr 10, 2017 at 1:05 PM, Thomas <tho...@dateiliste.com> wrote: > On 2017-04-10 20:00, Scott Robison wrote: >> >> On Apr 10, 2017 12:48 PM, "Thomas" <tho...@dateiliste.com >> <mailto:tho...@dateiliste.com>> wrote: >> Example of .

Re: [fossil-users] Issue with ignore-glob

On Apr 10, 2017 12:48 PM, "Thomas" wrote: Hello, As stated in one of my earlier mails, I also got an issue with files to ignore. I have now created a folder .fossil-settings and placed the glob files in it. Actually, I got a batch file that reads the file filter

Re: [fossil-users] Issue with ignore-glob

t seems to have been put in place to check either the file in the repo or the file on the disk depending on what is available. I don't have time to understand it completely, but that seems to be the source of my confusion as to when / where versioned settings are ac

Re: [fossil-users] Issue with ignore-glob

On Tue, Apr 11, 2017 at 10:36 AM, Thomas <tho...@dateiliste.com> wrote: > On 2017-04-11 05:22, Scott Robison wrote: >> >> Perhaps it should be documented, but I don't think it is a bug. It is >> the software doing the job it was originally told to do (track versions >

Re: [fossil-users] Issue with ignore-glob

On Tue, Apr 11, 2017 at 2:31 PM, David Mason <dma...@ryerson.ca> wrote: > > On 11 April 2017 at 14:34, Scott Robison <sc...@casaderobison.com> wrote: >> >> No, it is an explicit command clearly stating the user's desire for >> exclusion of these files *that

Re: [fossil-users] Issue with ignore-glob

On Tue, Apr 11, 2017 at 4:11 PM, Thomas <tho...@dateiliste.com> wrote: > On 2017-04-11 22:51, Scott Robison wrote: >> >> On Tue, Apr 11, 2017 at 3:39 PM, Scott Robison <sc...@casaderobison.com> >> wrote: >>> >>> On Tue, Apr 11, 20

Re: [fossil-users] Issue with ignore-glob

On Tue, Apr 11, 2017 at 3:04 PM, Thomas <tho...@dateiliste.com> wrote: > On 2017-04-11 19:34, Scott Robison wrote: >> >> No, I try to explain why what you see isn't a design flaw, and >> apparently fail. But I'll keep trying! > > > Since I've never heard of any

Re: [fossil-users] Issue with ignore-glob

On Tue, Apr 11, 2017 at 3:11 PM, Thomas <tho...@dateiliste.com> wrote: > On 2017-04-11 22:01, Scott Robison wrote: >> >> On Tue, Apr 11, 2017 at 2:31 PM, David Mason <dma...@ryerson.ca> wrote: >>> >>> I think --ignore should give an err

Re: [fossil-users] Issue with ignore-glob

On Tue, Apr 11, 2017 at 3:21 PM, Thomas <tho...@dateiliste.com> wrote: > On 2017-04-11 22:11, Thomas wrote: >> >> On 2017-04-11 22:01, Scott Robison wrote: >>> >>> I was thinking about that earlier (well, a warning, not an error, >>> which presum

Re: [fossil-users] Issue with ignore-glob

On Tue, Apr 11, 2017 at 3:39 PM, Scott Robison <sc...@casaderobison.com> wrote: > On Tue, Apr 11, 2017 at 3:21 PM, Thomas <tho...@dateiliste.com> wrote: >> On 2017-04-11 22:11, Thomas wrote: >> >> add >>--ignoreIgnore unmanaged files matching &

Re: [fossil-users] Issue with crlf-glob *

On Apr 12, 2017 10:31 AM, "Thomas" wrote: On 2017-04-09 02:19, Richie Adler wrote: > Thomas decía, en el mensaje "[fossil-users] Issue with crlf-glob *" del > 8/4/2017 17:46:14: > > Does anyone know how to unveil the secret of getting the mentioned >> asterisk into the

Re: [fossil-users] Issue with crlf-glob *

On Apr 8, 2017 3:29 PM, "Thomas" wrote: On 2017-04-08 21:59, Richard Hipp wrote: > On 4/8/17, Thomas wrote: > >> >> C:\fos>fossil settings crlf-glob *.obj >> C:\fos> >> C:\fos>fossil settings crlf-glob * >> Usage: fossil settings ?PROPERTY? ?VALUE?

Re: [fossil-users] Issue with ignore-glob

On Apr 10, 2017 5:02 PM, "Thomas" <tho...@dateiliste.com> wrote: On 2017-04-10 22:28, Scott Robison wrote: > On Mon, Apr 10, 2017 at 2:57 PM, Thomas <tho...@dateiliste.com> wrote: > >> I reckon I owe you a beer! ;-) >> > > Not at all. I don't drink,

Re: [fossil-users] Issue with crlf-glob *

On Wed, Apr 12, 2017 at 2:10 PM, Thomas <tho...@dateiliste.com> wrote: > On 2017-04-12 18:01, Scott Robison wrote: >> >> On Apr 12, 2017 10:31 AM, "Thomas" <tho...@dateiliste.com >> <mailto:tho...@dateiliste.com>> wrote: >> >> On 201

Re: [fossil-users] Issue with crlf-glob *

On Wed, Apr 12, 2017 at 4:41 PM, Thomas <tho...@dateiliste.com> wrote: > On 2017-04-12 23:24, Scott Robison wrote: >> >> When I am using the download from fossil-scm.org, I am able to use >> single quotes to 'escape' the asterisk. Double quotes do not work. >

Re: [fossil-users] Support for commonmark markdown in fossil

On Sat, Mar 11, 2017 at 8:08 AM, Mark Janssen wrote: > Good questions. Currently it replaces the existing markdown parser which > can break existing files. This is why I suggested the repo wide setting. > Sorry, I missed that part. > There are other possible solutions

Re: [fossil-users] Support for commonmark markdown in fossil

g markdown support or be in addition to it? If replace, would it "break" existing repos that are using markdown? If people have .md files with the existing markdown support, might this need a different extension? -- Scott Robison ___ fossil-users mailing li

Re: [fossil-users] Problem with: fossil revert -r xxx

I'm on the road and may not be thinking clearly, but if you're trying to revert your entire tree to the state 6 or 7 commits ago, might it be easier to update to the commit you want, rename the first commit in the now unwanted branch, and continue on from the new root? -- Scott Robison

Re: [fossil-users] A tutorial about "branches", "trunks", "leafs", etc.?

On Apr 29, 2017 8:30 PM, "The Tick" wrote: OK, I think I've figured it out! You're supposed to do a fossil >open< with a version name being "trunk" (default) or "branch name". When finished, do a fossil close. It appears that I can even do this in separate directories at the

Re: [fossil-users] manifest setting "l" flag

On Sep 29, 2017 7:43 AM, "Andy Goth" <andrew.m.g...@gmail.com> wrote: On 09/28/17 21:34, Scott Robison wrote: > There is a winsymlink branch I created some time ago. Hasn't been kept > up to date (I didn't need it, just thought it might be useful for > feature parity

Re: [fossil-users] manifest setting "l" flag

There is a winsymlink branch I created some time ago. Hasn't been kept up to date (I didn't need it, just thought it might be useful for feature parity) but I could take a look at it if you were interested. Or you could. On Sep 28, 2017 7:08 PM, "Andy Goth" wrote: >

Re: [fossil-users] tangent vs. wyoung on recent commti

I'd bet that you can commit as anyone and push it if you have that access. You probably wouldn't keep that access for long, though. On Dec 14, 2017 12:13 PM, "Warren Young" wrote: > On Dec 14, 2017, at 10:19 AM, jungle Boogie > wrote: > > > > So

Re: [fossil-users] Fossil-NG Bloat?

On phone, apologies in advance for top posting... The value I see from multi vcs support isn't providing easy setup of hosting one repo on multiple formats (though that would be awesome). I like the idea of using fossil at work where I'm forced to use git (or Perforce, though that hasn't been

Re: [fossil-users] Lots of web interface changes

I read that as no, he isn't having the same problem. On Dec 6, 2017 2:59 PM, "Richard Hipp" wrote: > On 12/6/17, Stephan Beal wrote: > > On Wed, Dec 6, 2017 at 8:33 PM, Richard Hipp wrote: > > > >> know.) Are you still having the

[fossil-users] Dilbert Git

In reading today's Dilbert, I imagined how it applies to git: http://dilbert.com/strip/2018-05-02?utm_source=dilbert.com/newsletter_medium=email_campaign=brand-loyalty_content=strip-image -- Scott Robison ___ fossil-users mailing list fossil-users

Re: [fossil-users] Digital signatures on check-ins. Was: tangent vs. wyoung on recent commti

Forged should be a skull and crossbones. I would think yellow and red unlocked locks and green locked locks, but definitely with hover text for those of us with faulty color perception. On Dec 21, 2017 3:16 PM, "Richard Hipp" wrote: > On 12/21/17, jungle Boogie

Re: [fossil-users] Setting up an internet Fossil server

I've done similar work for my own lighttpd based personal server. If you'd like I can share my config, maybe it would be helpful. On Feb 26, 2018 1:36 PM, "Roy Keene" wrote: > Scott, > > Fossil can be run in any URL suffix on an existing domain. This > is how, for

<    1   2   3