For some time now I'm using
pdfLaTeX for writing my job applications, which normally contain 3 pdf documents all created with
- the letter of motivation
- the CV and more information about my projects
- diploma, certificates, etc.
I now noticed that it would have been good to use version control of the different versions to document the differences or take notes about what was changed.
I already used version control with the
svn-multipackage for my dissertation, but that is only a "linear" process where I save a "snapshot" and don't have different versions in parallel.
=> So what would be an appropriate workflow for SVN to handle those documents
under the following conditions:
- it should be clear in the .tex source which document/version was taken as "template" for the actual file, but this shall not be visible in the pdf
(to avoid the potential employer seeing "ah, this is application number 323a ...")
- I'll create a directory for each application "somewhere" outside my svn repository,
-> I think this would be done by an
exportof an existing version - is that correct?
(That directory will also contain other documents with information about the company, the job etc., which will not be managed by svn)
- If the documents are finished, is it correct to save them in the repository by 'update'?
- How could I create different "main versions"
(e. g. one focussing on jobs in IT business which puts more emphasize on my computer skills and another one for the more "technical" jobs where those computer skills are not shown in detail)
- Would it be a problem for SVN if in the custom directory of each application I change the name of
I suppose when I do that and then send it back to the repository,
SVNwould be confused and not recognize the new document as a changed version of
I'm sorry if that sounds like stupid questions, but I have no experience with the "real" use of svn up to now. :-(