I have seen variations on this question on stackoverflow, but never a definitive answer as most of them just tell people to change the workflow.
Yes, I know how SVN works and how to ignore files on a commit, but is there any way to actually ignore conflicts (i.e., a direct answer to How to ignore conflicts in tortoiseSVN) ?
Here is the workflow:
I have several coauthors working on a latex file, some are compiling to a PDF and others are just reading the compiled document.
Some will never compile the file directly (in fact, will not even have latex setup!), but want to get access to the latest copy of the compiled PDF.
I don't really care if the PDF gets a little out of date with the commits when being actively worked on, but I still want to be able to tell the coauthor who isn't compiling the paper to access the latest commited copy.
For those who are editing the latex file, some are not very technical and constant source of SVN conflicts when doing an update on the server is annoying and confusing.
Is there anyway to put in a property in SVN to ignore local changes and overwrite the local changes? Since the less technical users would be using tortoiseSVN, it is fine if the solution is specific to that product. Of course, I only would want to associate this with particular files.