The canonical answer to these situations is to file all the different types
of files in different subdirectories, so the Linux team only checks out the
"/trunk/linux" directory, the windows people check out "/trunk/win32", and
for a complete checkout you check out "/trunk".
Your Situation 1 sounds harder to fix this way, but that may be because I
don't understand what separates the 50 files from the other 950. If there's
some easily-definable criterion (partial filename? extension?) then it
should be trivial.
> -----Original Message-----
> From: Den Varaksin [mailto:d.varaksin@compassplus.ru]
> Sent: Friday, July 23, 2004 6:51 AM
> To: users@subversion.tigris.org
> Subject: Subversion filter?
>
>
> Hello!
>
> Situation 1
> There is a catalogue in repository for example with 1000 files.
> Each of users works only with the set of files (for example,
> 50) and don't want to see
> superfluous 950 files in his working copy.
>
> Situation 2
> There is a crossplatform project. Besides the general files
> (for Windows, Linux, Sun...) there are the files
> belonging to a concrete platform (for example, makefiles for Linux).
> But Windows users do not want to see files for Sun, Linux and others.
>
> Possible solution
> Users can create group of files using properties (for
> example, non-windows, non-linux, my_files).
> I create a program which reads properties of all files in
> a working copy and deletes files that satisfy filter.
>
> But can be there are other variants?
>
> Thanks
> Den
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 23 15:17:57 2004