Re: [fossil-users] Incomplete patch with idea for enhancement

On Apr 18, 2017, at 8:07 PM, The Tick wrote: > > I added this patch: > > --- doc.c.orig 2017-03-10 11:07:08.0 -0600 > +++ doc.c 2017-04-17 23:32:03.770418400 -0500 > @@ -49,6 +49,7 @@ > { "\211PNG\r\n\032\n", 8, "image/png" }, > { "\377\332\377",3, "imag

Re: [fossil-users] Feature request: local .fossil-ignore

On 18 April 2017 at 18:04, Ross Berteig wrote: > > No, the wild cards in the glob can match any part of the path. You can > ignore "*/_build/*" and that will ignore any folder named _build and all > its descendants anywhere in the tree except at the root of the workspace. But if I want to *not*

[fossil-users] Incomplete patch with idea for enhancement

I'm very new to fossil so maybe there's a way to do this already. After I had committed a PNG to a fossil repository then fossil UI showed the PNG itself instead of just its name. Pretty nice! After adding an ICO, fossil just said it was XXX number of bytes. After looking at the source, I add

Re: [fossil-users] REST API and client for same

OK, so I don't think there's any interest in this beyond me :-( On Wed, Apr 5, 2017 at 1:58 PM, Paul Hammant wrote: > I don't really need Fossil to become an application server. I just need > it to handle CRUD over HTTPS on specific resources, and have configurable > permissions for that. Thou

Re: [fossil-users] Feature request: local .fossil-ignore

On 4/18/2017 2:29 PM, rosscann...@fastmail.com wrote: @Barry: True, but it's clumsy, since you have to specify every path, in full, in the global ignore-glob file. If you move a subproject to a different location in the directory tree, you have to remember to update the ignore-glob file. No,

Re: [fossil-users] Feature request: local .fossil-ignore

On Wed, Apr 19, 2017 at 07:29:42AM +1000, rosscann...@fastmail.com wrote: > @Barry: True, but it's clumsy, since you have to specify every path, in > full, in the global ignore-glob file. If you move a subproject to a > different location in the directory tree, you have to remember to update > the

Re: [fossil-users] Feature request: local .fossil-ignore

On 4/18/2017 2:21 PM, Barry Arthur wrote: This is already possible with pathed globs in your .fossil-settings/ignore-glob file. On 19 April 2017 at 01:10, David Mason > wrote: I have had to use Git for something this semester. It was mostly a failure and I'

Re: [fossil-users] How to deal with obsolete stuff in a repository

On Apr 17, 2017, at 8:26 PM, The Tick wrote: > > On 4/17/2017 9:11 PM, Ross Berteig wrote: >> Try to avoid >> preserving a version number as part of the folder names in the workspace >> even if your upstream does that to you. > > So I've goofed up by putting freetype-2.7.1/ and others into the r

Re: [fossil-users] How to deal with obsolete stuff in a repository

On 4/17/2017 7:26 PM, The Tick wrote: . So I've goofed up by putting freetype-2.7.1/ and others into the repository? "Goofed up" is too strong. "Picked a different way to do it" is more accurate. There are tradeoffs and a lot of personal preference involved. I guess I had assumed that

Re: [fossil-users] Feature request: local .fossil-ignore

@Barry: True, but it's clumsy, since you have to specify every path, in full, in the global ignore-glob file. If you move a subproject to a different location in the directory tree, you have to remember to update the ignore-glob file. This is something I miss from Subversion (and Git, too, appare

Re: [fossil-users] Feature request: local .fossil-ignore

This is already possible with pathed globs in your .fossil-settings/ignore-glob file. On 19 April 2017 at 01:10, David Mason wrote: > I have had to use Git for something this semester. It was mostly a > failure and I'll find a way to use fossil going forward. > > That said, I noticed one featur

Re: [fossil-users] Is there a way to find identical files?

Tony Papadimitriou wrote: [snip] For example, if /defs.inc is the same as /project1/defines.inc, and project2/lib.mod is the same as project3/library.inc and project4/libroutines.inc, and docs/mydocs.pdf is the same as project1/docs.pdf, I would like some simple report like this: defs.inc pr

[fossil-users] Feature request: local .fossil-ignore

I have had to use Git for something this semester. It was mostly a failure and I'll find a way to use fossil going forward. That said, I noticed one feature of Git that was very useful, and I'd love to see in Fossil. In Git, you can have a .gitignore file in any directory and it applies to that

Re: [fossil-users] How to deal with obsolete stuff in a repository

Another option is to create a fossil for the 3rd party libraries, and then open that fossil --nested in a directory inside your working directory. Then nothing in that nested directory tree will be part of the main fossil. You don't even need to commit to it if you don't want. Lastly, when you do