[fossil-users] Bug with fossil flattening tree during a 'fossil mv'

2010-06-24 Thread Michael Barrow
I wanted to move a directory up in the tree. Notice how fossil flattened the html subdir (highlighted in bold). Is this a bug or feature? Version: [73c24ae363] 2010-03-18 14:20:33 UTC crazy-arms:Projects $ fossil mv fstc/35c/* 35c/ RENAME Projects/fstc/35c/35c.pl Projects/35c/35c.pl RENAME Proje

Re: [fossil-users] fossil rm ./*

2010-06-24 Thread Kohn Bernhard
Oh no, I didn't meant to say, its important. And yes, you are right, I use this for an obscure corner case, and doing this with commandline is no problem. Best regards Bernhard ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://li

Re: [fossil-users] ticket notifications

2010-06-24 Thread Jacek Cała
Thanks for ideas I'll try to play with this. Jacek 2010/6/24 Joshua Paine > On 06/24/2010 02:39 PM, Jacek Cała wrote: > > Regarding tickets notification, it would be nice if opening/closing > > tickets allow starting/stopping time measurement. In this way fossil > > could count up how long it

Re: [fossil-users] ticket notifications

2010-06-24 Thread Joshua Paine
On 06/24/2010 02:39 PM, Jacek Cała wrote: > Regarding tickets notification, it would be nice if opening/closing > tickets allow starting/stopping time measurement. In this way fossil > could count up how long it takes to complete tasks. IMO this is way, way out of scope for fossil, but it wouldn't

Re: [fossil-users] ticket notifications

2010-06-24 Thread Eric
> Regarding tickets notification, it would be nice if opening/closing > tickets > allow starting/stopping time measurement. In this way fossil could count > up > how long it takes to complete tasks. This would be more intentional than > in > eclipse's mylyn but still very useful. > > Regards, >

Re: [fossil-users] ticket notifications

2010-06-24 Thread Ron Aaron
On Thursday 24 June 2010 21:28:15 Richard Hipp wrote: > There is nothing in principle that would prevent such functionality from > being added. But on the other hand, no such functionality currently exists. I'm happy using the RSS feed feature to get notifications when things change; I suppose i

Re: [fossil-users] ticket notifications

2010-06-24 Thread Jacek Cała
Regarding tickets notification, it would be nice if opening/closing tickets allow starting/stopping time measurement. In this way fossil could count up how long it takes to complete tasks. This would be more intentional than in eclipse's mylyn but still very useful. Regards, Jacek 2010/6/24 R

Re: [fossil-users] ticket notifications

2010-06-24 Thread Richard Hipp
There is nothing in principle that would prevent such functionality from being added. But on the other hand, no such functionality currently exists. Notice that the issue is complicated by the fact that ticket changes can occur on disconnected systems. When are the emails sent? When the disconn

Re: [fossil-users] fossil rebase

2010-06-24 Thread Richard Hipp
I think that after a git-rebase or a fossil-merge, the content of the leaves of all branches are the same. The difference is that with git-rebase, you have rewritten the history of the branch so that whereas in reality development of the "topic" branch began with version E, A---B---C top

[fossil-users] ticket notifications

2010-06-24 Thread Jeff Rogers
Hi all, Is there a way to set up the ticket system to send email notifications when a ticket is created (or changed, etc)? There doesn't appear to be any way in TH1 to run an external command (like sendmail) Alternately, is there a command-line way to list any tickets created in the past X (e

Re: [fossil-users] fossil rebase

2010-06-24 Thread Eric
> I'm not sure. Is there really no difference? > > - Altu > > I was going to mention the merge too - I think that the resulting leaf would be the same, but the tree would not have been re-arranged. You **do not** change history. The principle is the same as in accounting, where you should not e

Re: [fossil-users] fossil rm ./*

2010-06-24 Thread Jeff Rogers
Kohn Bernhard wrote: > Hello all, > > > > I have experienced following behavior when removing files. > > > > I open a repository. I would like to delete all files, so I use > > fossil rm ./* > > In the output of the commandline the filenames (also with > subdirectories) with DELETED in f

Re: [fossil-users] fossil rm ./*

2010-06-24 Thread Richard Hipp
On Thu, Jun 24, 2010 at 10:37 AM, Kohn Bernhard wrote: > Hello all, > > > > I have experienced following behavior when removing files. > > > > I open a repository. I would like to delete all files, so I use > > fossil rm ./* > > In the output of the commandline the filenames (also with subdirecto

[fossil-users] fossil rm ./*

2010-06-24 Thread Kohn Bernhard
Hello all, I have experienced following behavior when removing files. I open a repository. I would like to delete all files, so I use fossil rm ./* In the output of the commandline the filenames (also with subdirectories) with DELETED in front appeared. When I try to commit the deleted files wit

Re: [fossil-users] usage of fossil settings ignore-glob in combination with add and commit

2010-06-24 Thread Richard Hipp
On Thu, Jun 24, 2010 at 9:28 AM, Kohn Bernhard wrote: > Hello all, > > > > thank you very much, with the batch-script I have the functionality I > needed! > > > > But notheless, should add not behave like extras and changes in respect to > the ignore-glob setting? > Yes, probably so. I'll make

Re: [fossil-users] usage of fossil settings ignore-glob in combination with add and commit

2010-06-24 Thread Kohn Bernhard
Hello all, thank you very much, with the batch-script I have the functionality I needed! But notheless, should add not behave like extras and changes in respect to the ignore-glob setting? best regards Bernhard ___ fossil-users mailing list foss

Re: [fossil-users] fossil rebase

2010-06-24 Thread Michael Richter
I'm not a git user, so I have no idea. On 24 June 2010 18:56, wrote: > I'm not sure. Is there really no difference? > > - Altu > > > > -Original Message- > From: Michael Richter > To: fossil-users@lists.fossil-scm.org > Sent: Thu, Jun 24, 2010 4:23 pm > Subject: Re: [fossil-users] fossi

Re: [fossil-users] fossil rebase

2010-06-24 Thread altufaltu
I'm not sure. Is there really no difference? - Altu -Original Message- From: Michael Richter To: fossil-users@lists.fossil-scm.org Sent: Thu, Jun 24, 2010 4:23 pm Subject: Re: [fossil-users] fossil rebase What does this do that fossil merge trunk from my branch in ttmrichter doesn't

Re: [fossil-users] usage of fossil settings ignore-glob in combination with add and commit

2010-06-24 Thread Kohn Bernhard
Hello all, I had this situation on a windows system (windows server 2003) Best regards Bernhard ___ 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] usage of fossil settings ignore-glob in combination with add and commit

2010-06-24 Thread Kevin Greiner
On Thu, Jun 24, 2010 at 7:24 AM, Kohn Bernhard wrote: > But when I run fossil add . to add all the files, every file and also the > ones which applies to the ignore-glob setting are added. If I commit then, > also the not wanted files are added to the repository. Exist there a way, > that only fi

[fossil-users] usage of fossil settings ignore-glob in combination with add and commit

2010-06-24 Thread Kohn Bernhard
Hello all, I started recently to use fossil for a small software project, and I must say, I am very pleased how easy it is to use! But I have a problem using the ignore-glob settings together with add and commit. If I understand it the right way, the ignore-glob settings prevents one from comm

Re: [fossil-users] fossil rebase

2010-06-24 Thread Michael Richter
What does this do that *fossil merge trunk* from my branch in *ttmrichter* doesn't do? On 24 June 2010 16:31, wrote: > Well, you have custom changes (A, B, C) in a branch and you want to > keep up with latest changes happening in trunk - at frequent intervals. > > What rebase does is it applies

Re: [fossil-users] fossil rebase

2010-06-24 Thread altufaltu
Well, you have custom changes (A, B, C) in a branch and you want to keep up with latest changes happening in trunk - at frequent intervals. What rebase does is it applies your changes A, B & C to new head (G) with a knowledge of everything that has happened between E & G. If any of A, B or C wa