Hello Gunnar!
> Regarding enhancements I stumbled about an issue I noted some time ago with
> ignore list behavior.
> When new filter rules are applied to (or remove from) ignore list you still
> need
> to add/unversion appropriate files manually.
Well, it's the behaviour of subversion and git (and, IIRC, mercurial, etc.
too), that an
ignore list is used for detecting *which files should be versioned*.
But it may not change the list of files that are already known, kept and stored.
The basic idea was that the patterns are used for removing noise from "status"
display -
ie entries that are not versioned.
"fsvs add" should have priority, so that I can always define exceptions to the
rules.
> How hard would it be to implement some enhancement to run add/unversion
> internally when ignore list is modified and will that break the philosophy
> behind ignore list? I'd admit a sense to keep add/unversion for someone but
> the
> disadvantage is that you loose an overview of the filtered files. Thats what
> IMO
> the ignore list should also be used for. What is your point on this?
Well, I could certainly imagine a command that synchronizes the filelist
against the
ignore patterns.
Or perhaps an option for commit; but I think the extra command would be better.
(If you make it an option, you could set it in your config - that would suit
your kind
of work better.)
How about "filelist-sync"? No, too general.
Hmmm, "sync" and "ignore" as prefixes are already well-established ... so it
should be
something different.
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
------------------------------------------------------
http://fsvs.tigris.org/ds/viewMessage.do?dsForumId=3923&dsMessageId=2653549
To unsubscribe from this discussion, e-mail: [[email protected]].
