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
On Fri, 3 Feb 2012 09:57:47 -0700 Matt Welland wrote:
> > > If I do:
> > >
> > > fossil rm some/file.txt
> > > rm some/file.txt
> >
> > fossil commit
> >
>
> People often prefer to commit when their work has reached some level
> of completion or readiness and partially done commits can cause
> un
On Fri, Feb 3, 2012 at 11:18 AM, Matt Welland wrote:
> If I do:
>
> fossil rm some/file.txt
> rm some/file.txt
> ...do stuff...
> fossil update
>
> then some/file.txt is resurrected which is really really annoying when you
> just got your build to work and then because files that shouldn't be the
I think part of the original post was whether the documentation was
correct. i.e., it says uncommitted changes are retained. I would argue that
"fossil rm" is an uncommitted change, which should be retained. Either the
documentation is wrong or there is a bug w.r.t. "fossil rm".
As a work around,
On Fri, Feb 3, 2012 at 10:57 AM, Matt Welland wrote:
> On Fri, Feb 3, 2012 at 9:46 AM, Dmitry Chestnykh
> wrote:
>> On Fri, 3 Feb 2012 09:18:32 -0700 Matt Welland wrote:
>> > If I do:
>> > fossil rm some/file.txt
>> > rm some/file.txt
>> fossil commit
> People often prefer to commit when their wo
On Fri, Feb 3, 2012 at 9:46 AM, Dmitry Chestnykh wrote:
> On Fri, 3 Feb 2012 09:18:32 -0700 Matt Welland wrote:
>
> > If I do:
> >
> > fossil rm some/file.txt
> > rm some/file.txt
>
> fossil commit
>
People often prefer to commit when their work has reached some level of
completion or readiness a
On Fri, 3 Feb 2012 09:18:32 -0700 Matt Welland wrote:
> If I do:
>
> fossil rm some/file.txt
> rm some/file.txt
fossil commit
--
Dmitry Chestnykh
http://www.codingrobots.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists
If I do:
fossil rm some/file.txt
rm some/file.txt
...do stuff...
fossil update
then some/file.txt is resurrected which is really really annoying when you
just got your build to work and then because files that shouldn't be there
suddenly reappear and things break.
I can see where might be some c
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
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
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
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
17 matches
Mail list logo
