Login | Register
My pages Projects Community openCollabNet

Discussions > dev > Re: [feature request] auto unversion of files matching new ignore pattern

Discussion topic

2020-03-13: This site is going to be decommissioned and shut down very soon. Please copy and archive any data you wish to keep ASAP

Hide all messages in topic

All messages in topic

Re: [feature request] auto unversion of files matching new ignore pattern

Author pmarek
Full name P.Marek
Date 2008-10-01 09:06:41 PDT
Message Hello Gunnar!

On Tuesday 30 September 2008 Gunnar Thielebein wrote:
> It would be nice if fsvs would have an option that if patterns are
> edited files that are matched also automagically become unversioned.
> If I have added some pattern like
> > ./etc/gshadow-
> It should automaticly appear as unversioned:
> > .d.. ./etc/gshadow-
> IMO this was already requested some time ago.
> I think adding a config for that would also not break too much
> compatibility of older versions.
Yes, it would have to be some config option, because that would mean trying
*all* patterns on *all* known entries ... and that can take some time, and
possibly include entries that you want to keep.

> It is that you cant have the ultimate ignore list matching all kind of
> distribution.
> Easing the use of the unversion would help in customising hosts.
Yes, that's right ...
Maybe the inverse - doing "unversion" with some flag puts a take-pattern in
front of the list? But the shell expands wildcards, whereas FSVS doesn't ...
so you'd get a whole lot of take-patterns.

> At the moment I need to edit the ignore list, then unversion the files
> and if some other admin has done work also remember the pathes i removed.
> What do you think about that?
Well, since some time I've got a point on my TODO ... "fsvs shelf"
and "unshelf" or something like that.
That should mark all local changes as not-changed, so that only new changes
appear (and get committed) - and on "unshelf" they get visible again.

But that should work in multiple layers, and possibly many changes in a single
file should be splitted into the various shelves, etc. ....

Kind of what quilt does: http://savannah.nong​nu.org/projects/quil​t

But I have no real idea how that can be sanely implemented.

Currently I'd like to keep that behaviour as-is - trying a hundred patterns
against some hundred thousand paths isn't nice.

But if you really insist, we can discuss further which solution you could
implement ;-)



Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!
Messages per page: