>
> There are some files that you don't necessarily want committed -
>> intermediates such as object files, IDE "droppings", etc. Obviously, your
>> mileage may vary and it might be a requirement for your workplace/style.
>> Avoiding the intermediates could be done with ignore filters, but we've
>> seen that these aren't universally applied.
>
>
> Not sure that I understand you correctly.... Why not ignore them? Is here
> some cases when it is undesirable?
>
> What I meant was that the ignore filters have cases where they don't seem
> to work as expected. There have been several threads in this discussion
> list about that. I believe the normal response is to adjust what people
> expect.
>
> But yes, there are *some* cases where it's undesirable. For example, if
> you have purchased a third-party library that's only available as an object
> file, but at the same time your version control regime is such that object
> files from your compiler should not be committed (and they use the same
> extension), then you definitely want *not* to ignore the third-party
> library, but *do* want to ignore the intermediate files.
>
>
No problem. Say it is .lib file.
Add *.lib to ignores.
=> No compiler files, no third paty library in commit dialog displayed as
non-versioned.
Go to third party library in coinsole/expolrer. Add file - svn allow this.
Commit.
=> third party librray added, compiler output not visible.
Change third party library (to new version). Now it will be visible in
commit dialog and allowed to be commited.
Ignores has affect only on files displayed as non-versioned. If file
already added to source control, it will not be affected by ignores
anymore. It can be updated, deleted, modified.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3088626
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-09-17 14:17:31 CEST