On Dec 13, 2017, at 2:21 PM, Zakero wrote:
>
> The "fossil clean" command has the "--emptydirs" option. That might be
> useful for the "rm" command as well.
If Fossil got that option, I’d probably forget that it existed a week after the
change went in. I’d end up saying something like
$
On Wed, Dec 13, 2017 at 3:01 PM, Warren Young wrote:
> On Dec 13, 2017, at 1:03 PM, jungle Boogie
> wrote:
> >
> > On 13 December 2017 at 07:58, Warren Young wrote:
> >
> >> I’d feel differently if Fossil owned the directories, but it doesn’t.
> They’re mine; leave them alone!
> >
> > Yes, I ag
On Dec 13, 2017, at 1:03 PM, jungle Boogie wrote:
>
> On 13 December 2017 at 07:58, Warren Young wrote:
>
>> I’d feel differently if Fossil owned the directories, but it doesn’t.
>> They’re mine; leave them alone!
>
> Yes, I agree. I think this topic has been raised here in the past,
> altho
On 13 December 2017 at 07:58, Warren Young wrote:
> I’d feel differently if Fossil owned the directories, but it doesn’t.
> They’re mine; leave them alone!
Yes, I agree. I think this topic has been raised here in the past,
although that was about removing files. Still, If I created the
directo
On Dec 13, 2017, at 6:21 AM, Tino Lange wrote:
>
> The directory/directories will keep existing!
Given that Fossil doesn’t know anything about directories, other than as
containers for the files it manages, I’m not sure that isn’t the right thing.
To have Fossil remove intermediate directories
Hi!
When doing a
$ fossil rm --hard dir1
it will unregister from fossil and then delete all files within the
'dir1' hierarchy.
But: The directory/directories will keep existing!
I need to do a
$ rm -rf dir1
afterwards (so the whole --hard is mostly needless, since I need to do
the additional
6 matches
Mail list logo