Re: [fossil-users] removing a large directory

I tried that, of course. It didn't work. On Fri, Apr 13, 2012 at 11:06 PM, vince wrote: > I think that by "fossil rm name_of_the_directory", it deletes the entire > directory. > > Le 14/04/2012 07:39, Russ Paielli a écrit : > > I removed an entire directory from my filesystem. It contained hund

Re: [fossil-users] removing a large directory

On Sat, 14 Apr 2012 08:06:37 +0200, you wrote: > I think that by "fossil rm name_of_the_directory", > it deletes the entire directory. And if that doesn't work, there's always the unix way: fossil rm $( fossil ls | grep "/directory/" ) >Le 14/04/2012 07:39, Russ Paielli a écrit : >> I removed

Re: [fossil-users] removing a large directory

I think that by "fossil rm name_of_the_directory", it deletes the entire directory. Le 14/04/2012 07:39, Russ Paielli a écrit : I removed an entire directory from my filesystem. It contained hundreds of data files. Now I want to remove it from my fossil repository, but I don't want to remove e

[fossil-users] removing a large directory

I removed an entire directory from my filesystem. It contained hundreds of data files. Now I want to remove it from my fossil repository, but I don't want to remove each file individually. The fossil rm command does not seem to take wild cards or accept a recursive command-line option. What is the

Re: [fossil-users] turning off gpg

On Saturday, April 14, 2012, James Turner wrote: > On Sat, Apr 14, 2012 at 01:19:11AM +0200, Marek wrote: >> I'm sorry should have been "before running fossil init" so fossil is set to clearsign off before I init a new repository but it still keeps looking for gpg. Am I doing something wrong or co

Re: [fossil-users] fossil: unable to create directory /var/tmp

On Fri, Apr 13, 2012 at 3:04 PM, Richard Hipp wrote: > fossil test-canonical-name / /var /var/tmp > fossil test-canonical-name / /var /var/tmp [/] -> [/] file_size = 4096 file_mtime = 1334361705 file_isfile = 0 file_isfile_or_link = 0 file_islink = 0 file_isexe = 0 fil

Re: [fossil-users] turning off gpg

On Sat, Apr 14, 2012 at 01:19:11AM +0200, Marek wrote: > I'm sorry should have been "before running fossil init" so fossil is set to > clearsign off before I init a new repository but it still keeps looking for > gpg. Am I doing something wrong or could this be a bug? > > thanks, > > Marek >

Re: [fossil-users] turning off gpg

On Fri, Apr 13, 2012 at 7:19 PM, Marek wrote: > I'm sorry should have been "before running fossil init" so fossil is set > to clearsign off before I init a new repository but it still keeps looking > for gpg. Am I doing something wrong or could this be a bug? > Looking at the code, I don't see a

Re: [fossil-users] turning off gpg

I'm sorry should have been "before running fossil init" so fossil is set to clearsign off before I init a new repository but it still keeps looking for gpg. Am I doing something wrong or could this be a bug? thanks, Marek . Original Message From：Marek Time：4/13/2012 18:3

Re: [fossil-users] More case-sensitive problems on Windows

Thanks. Problem should be fixed now. Case-insensitive filenames are a never-ending source of bugs. If you keep looking, I'm sure you'll find more. On Fri, Apr 13, 2012 at 6:11 PM, Jos Groot Lipman wrote: > ** > When I run the following sequence of commands on Windows, fossil gets > confused b

[fossil-users] More case-sensitive problems on Windows

When I run the following sequence of commands on Windows, fossil gets confused because I add one file from Folder and the other from folder. When I browse in the GUI for the 'Files' only file1 in 'Folder' is shown, not file2. It does show up when I press 'All' in the interface. It seems the 'case-s

Re: [fossil-users] fossil: unable to create directory /var/tmp

On Fri, Apr 13, 2012 at 5:07 PM, Matt Welland wrote: > We are seeing the following error in some users environments and I have > not been able to root cause it yet. Does anyone have suggestions on how to > debug this? > > > fossil gdiff --from abce3460ac --to c628b11818 ./abcdef.rb > fossil: unab

[fossil-users] fossil: unable to create directory /var/tmp

We are seeing the following error in some users environments and I have not been able to root cause it yet. Does anyone have suggestions on how to debug this? > fossil gdiff --from abce3460ac --to c628b11818 ./abcdef.rb fossil: unable to create directory /var/tmp __

Re: [fossil-users] Request feature : choose directory for the addremove command

On Fri, Apr 13, 2012 at 6:18 PM, vince wrote: > it's not a link. > I open it with the command : > d:\projects> fossil open d:\projects\myproject1\myproject1.fossil > It is generally considered bad practice to have the .fossil file UNDER or IN the "open" target directory. That is the sou

Re: [fossil-users] Request feature : choose directory for the addremove command

yes, you're right. I tried with the command: d:\projects\myproject1> ..\fossil open myproject1.fossil and there it works! thank you! Le 13/04/2012 18:23, Tomek Kott a écrit : You are opening the "working directory" in the directory from which you call the command (fossil open). Thus, you ARE ope

Re: [fossil-users] turning off gpg

Hi James, I've set the global clearsign to off before running fossil unit, but it still tries to call gpg. my fossil version is 1.22 2012-03-19 5dd5d39e7c. thanks, Marek . Original Message From：James Turner Time：4/13/2012 15:08 To：Fossil SCM user's discussion Subject：R

Re: [fossil-users] Request feature : choose directory for the addremove command

You are opening the "working directory" in the directory from which you call the command (fossil open). Thus, you ARE opening the working directory into d:\projects. hence, fossil addremove adds everything in d:\projects and below. Hence the issues you are seeing. Tomek On Fri, Apr 13, 2012 at 12

Re: [fossil-users] Request feature : choose directory for the addremove command

it's not a link. I open it with the command : d:\projects> fossil open d:\projects\myproject1\myproject1.fossil Le 13/04/2012 18:11, Stephan Beal a écrit : On Fri, Apr 13, 2012 at 5:37 PM, vince > wrote: I have a repo as follows: d:\projects\myproject1\myproject1.f

Re: [fossil-users] "ignore-glob" and case sensitive

On Fri, Apr 13, 2012 at 5:57 PM, Ramon Ribó wrote: > > Wouldn't it be more logical that > > fossil settings ignore-glob > > followed the case criteria of: > > fossil settings case-sensitive > That would be the most obvious (and simplest to implement), i think. But then you're lim

Re: [fossil-users] "ignore-glob" and case sensitive

it's true! Le 13/04/2012 17:57, Ramon Ribó a écrit : Wouldn't it be more logical that fossil settings ignore-glob followed the case criteria of: fossil settings case-sensitive ? RR 2012/4/13 Stephan Beal > On Fri, Apr 13, 2012 at 3:10 P

Re: [fossil-users] Request feature : choose directory for the addremove command

On Fri, Apr 13, 2012 at 5:37 PM, vince wrote: > I have a repo as follows: d:\projects\myproject1\myproject1.fossil > When I open the repo, the file _FOSSIL_ is in d:\projects\ > Then you're opening it from that directory. Or perhaps projects or myproject1 is a Windows LNK (we've had some weird p

Re: [fossil-users] "ignore-glob" and case sensitive

Wouldn't it be more logical that fossil settings ignore-glob followed the case criteria of: fossil settings case-sensitive ? RR 2012/4/13 Stephan Beal > On Fri, Apr 13, 2012 at 3:10 PM, vince wrote: > >> the option "ignore-glob" is case sensitive. >> > > 0.02 Euro: My sugg

Re: [fossil-users] "ignore-glob" and case sensitive

yes, the optionignore-like would be a good solution! Le 13/04/2012 17:29, Stephan Beal a écrit : On Fri, Apr 13, 2012 at 3:10 PM, vince > wrote: the option "ignore-glob" is case sensitive. 0.02 Euro: My suggestion would that we add ignore-like as a new option, the

Re: [fossil-users] Request feature : choose directory for the addremove command

Hello, I have not created my repo at the root of my drive. For example, I have fossil.exe in d:\projects\ I have a repo as follows: d:\projects\myproject1\myproject1.fossil When I open the repo, the file_FOSSIL_ is in d:\projects\ Whenever it is in the same directory as fossil.exe I don't know ho

Re: [fossil-users] "ignore-glob" and case sensitive

On Fri, Apr 13, 2012 at 3:10 PM, vince wrote: > the option "ignore-glob" is case sensitive. > 0.02 Euro: My suggestion would that we add ignore-like as a new option, the difference being that ignore-glob uses (like now) a GLOB comparison (case-sensitive) and ignore-like would use a LIKE comparis

Re: [fossil-users] Request feature : choose directory for the addremove command

On Fri, Apr 13, 2012 at 5:59 AM, vince wrote: > Hello, > > the command "addremove" synchronize the repository with the working > directory. > So that fossil adds files that have nothing to do with my projects, such > as the file fossil.exeitself! > We should be able to choose from which directory

[fossil-users] "ignore-glob" and case sensitive

Hello, the option "ignore-glob" is case sensitive. We should be able to choose whether it is case sensitive or not. Thanks. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-

Re: [fossil-users] turning off gpg

On Fri, Apr 13, 2012 at 12:09:22AM +0200, Marek wrote: > Hi, > > I'd like to ask whether it's possible to turn off gpg signing entirely, for > example I've set clearsign to off and running: > fossil settings clearsign > gives me: > clearsign (global) off > Running commit however tells me that g

[fossil-users] Request feature : choose directory for the addremove command

Hello, the command "addremove" synchronize the repository with the working directory. So that fossil adds files that have nothing to do with my projects, such as the file fossil.exeitself! We should be able to choose from which directory we want to do the "addremove". Or we can change the wor

Re: [fossil-users] bug - should not be able to add tag to a ``Tag-change'' event.

A nice option for the search would be: fossil setting fulltextindex internal|external|off (default: off) internal would save the full text index in the same file than the database, external would save it in the ".fossil" file The full text index would record the version when a new word has been