ignore file type when update ?

[W.A]

Hi,

I have tried to use the ignore list feature as mentioned here : https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-ignore.html

Maybe I used it wrong but the behavior was not as I expected.

Let me explain:

The project I am working on involves many different type of engineers and artists.

Not all assets are necessary for everyone to get their work done.

For example, some artists need certain enormous 3D file assets while some other artists only need certain 2D assets.

Because of the project structure the folder hierarchy is deep and mixed of 2D and 3D assets.

The issue is, artists that only need 2D assets, when updating to latest, get all the 3D assets they don't need as well  (taking lots of download time and space on disk).

Is their a way to, on a user/local basis, ignore certain file types so they never get downloaded/updated on the users local PC while still being versioned in the projects repository for everybody that needs them to be present?

I used to do that when using Perforce.

Again, when I tried the Ignore List feature it ended up trying to delete & commit all file of the set file type from the entire project/repository!

Thank you very much in advance for your help.

Best

W.A

[Stefan]

you can only ignore non-versioned files. Once they're versioned, they're always downloaded and committed.

[Weston Norris]

As an alternative, perhaps you could have the 2d artists perform a "sparse checkout", which can be set up in the checkout dialog by clicking "Choose items", and deselecting the files and folders you don't want. 

Once you have a checkout with only the items you want, from there updating or checking in will only use the files you actually have as a part of your wc, so it should continue to be sparse as time goes on. (I do not know, however, if newly created  files in the repo would be included or excluded in future wc updates.) 

Something to keep in mind with a sparse checkout, though, is that there is no placeholders or anything for the items you skipped, so when looking at your working copy on disk you won't be able to see any of the files you had deselected. (It's kind of the point, you might say.) Since they are not part of your wc, suddenly when you move, delete, or rename folders, you might be affecting more or less of the repository than you intended, and any reorganization might have unintended consequences. (Disclosure time: I've never actually tried this to see what happens. It could be anything from an error code to chaos.)

At any rate, a sparse checkout would save disk space and download time as you desire, but could cause much confusion amongst the users if they try to move or rearrange files, for they are not working with the complete set of files anymore and may not appreciate the impact they are having on the other files they can't see. (Sparse checkouts usually get strongly recommended against for these sorts of reasons, but I've never actually used them in this way to know for sure.)

 

 -    Weston Norris

-------------------------------------------------------------------------------------------

--
You received this message because you are subscribed to the Google Groups "TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/53b00840-6eb0-4e18-8c59-f8cdeeb2caa7%40googlegroups.com.

[W.A]

This is very unfortunate... 

But thanks a lot for your answer anyway Stefan.

Norris, I didn't know about sparce checkout. Will give it a try, keeping in mind the caveat you mentioned.

Thanks!