1. ILC TDR SVN repository roll-out
Maura Barone
TDR Editorial Board Meeting
2 March 2012

2. TDR SVN repository
Repository :  (client access only)
The subversion repository can be accessed (check-in, checkout, update) through many different methods and clients (GUI) on local disk.
Ex. Cornestone/SmartSVN (MacOS), TortoiseSVN (Windows), subversion (Linux), you name it
Accounts : in mid January 2012 the TDR editors and PMs have been given personal accounts to access (read/write) the TDR-SVN repository.
If you misplaced your credentials or have problems in accessing the repository, please contact or
Browsing the TDR-SVN repository from the web :
(meant for authors and editors - requires Forge login,
mirror updated every 10 minutes – browse only, no write access from here)

3. TDR outline register on Forge:
For each chapter/section:
Directory name (ex. intro, bds, cfs, cost, …)
Filename (ex. tdr2_intro.tex)
Figure directory name (ex. tdr2/intro/figs)
LaTeX labels (ex. chapter:intro, or sec:scrf:ml_params)

4. TDR /trunk repository layout
The repository is organized in three directories:
+ trunk
+ tdr1
+tdr2
+ tags
+ branches
/trunk contains the most current
TeX source files and images, and
is organized in two subdirectories
(tdr1, tdr2). This is where you work
and commit your edits.

5. SVN cheat sheet First time only:  SVN checkout to local directory
Provide URL (path) of the repository, that is
(full repository)
Any time you plan to make new edits:
 SVN update
 [the real work] … make your edits … compile your file to make sure there are no LaTeX errors … look at the pdf output …
 SVN status
Check the status of your local working files (GUIs will typically show icons or status colors to indicate modified/new/missing/ files…)
 SVN commit
Check/review changes made (typically listed in a pop-up window)
Mandatory: enter a short description of the commit

6. SVN keywords DO NOT EDIT ! Your edits start here
SVN keywords (HeadURL, LastChangedDate, LastChangedRevision, and LastChangedBy) provide information about the last modification made to the file and are listed at the beginning of each .tex file in the repository. This information will be displayed in the footer of the draft TDR
SVN automatically updates this information – no action is required on your side
Note: if someone else commits a change to myfile.tex, your copy of that file will continue to display the same substituted keyword value as before—until you update your working copy. Remember to always update your working copy before starting your editing work.

7. Making the best use of SVN
It is desirable to regularly put submissions in SVN, so that we can keep a record of the various revisions
Text file formats : we accept LaTeX (.tex) files and Word (.docx)
Commit logical change-sets
When you commit a change to the repository, make sure your change reflects a single purpose, for instance the addition of a new subsection
File size: There is no theoretical limit to the size of the files SVN can handle.
files are sent "streamily" in both directions between Subversion client and server, using a small, constant amount of memory on each side of the network
be aware that large files may require some waiting time while SVN makes the copies, performs the diffs and send them to the server (more evident to remote users outside DESY)
Subversion commits are atomic (a change to a file is either completely stored or not stored at all) 

8. Authors can access old content from Forge: RDR
RDR-IR source files
Authors can access old content from Forge:
RDR
Interim Report
Please login for access to the document repositories and editing resources.  If you don't have an account, please register

9. Stay tuned at http://forge.linearcollider.org/tdr Support line

10. References
All things SVN: