On 31/08/10 17:10, P.Marek wrote:
> Hello Gunnar!
>
>> But the work begins if files needs to be sorted out because of
>> privacy or bloating the repo etc. I think fsvs behavior can, because of its
>> clueness and different use case, be different in that area. Comparing to svn 
>> the
>> fsvs ignore list is also more centric then some sporadic propsets containing
>> ignore rules.
>
>> I am also more for an option that changes the behaviour of "fsvs ignore".
> "fsvs ignore" is the wrong place - that's for editing the patterns.
>
>> What about something like "sync-with-ignore" defaulting to false? Would it be
>> necessary or even suffice to run a "sync-repos"?
> As an option which is used on "commit" it's ok.

For files that are already in version control the "fsvs commit" is for sure a 
good place. But what about the files that weren't commited yet und you want to 
get rid from "fsvs st"?

My intention is to trigger the add/unversion operations somehow when the ignore 
list is changed via  "fsvs ignore load/prepend/append/at=". Where do you think 
the storm breaks loose in the teacup?

>
> "sync-repos" is of course not needed - only the filenames have to be checked 
> against the
> filelist, and get added/unversioned as necessary.
>
> Or it could be used with "add" or "unversion" ...
>
>
> I'm sorry, I seem to have caused confusion with my remark about "sync-repos".
> I meant that there's already a command starting with the letters "sync", and 
> because
> FSVS accepts abbreviations a new command like "sync-with-ignore" could wreck 
> somebody
> trying to use "sync-repos".
> (Although, with one more thought, someone who does "sync-repos" must not care 
> about his
> WC list anyway.)

Sorry, to mix-up things with that question. I did a quick test for myself now 
and resulting did not care about ignore list changes.

Best,
Gunnar

>
>
> Regards,
>
> Phil
>

------------------------------------------------------
http://fsvs.tigris.org/ds/viewMessage.do?dsForumId=3923&dsMessageId=2653740

To unsubscribe from this discussion, e-mail: [[email protected]].

Reply via email to