<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
Eric and Alex,<br>
Perhaps this is a distraction, but it might save us from some
headaches once the changes/edits start coming fast a furious. I
created a "git" repository on the Jlab CUE machine. Everyone in the
positron group should have access. Git is available for
Linux/MacOS/Windows so everyone should be able to work with this. <br>
<br>
Here is how to get latest version of the proposal (assuming linux
command prompt):<br>
<ol>
<li>git clone
<a class="moz-txt-link-abbreviated" href="mailto:ssh://username@ifarml1/u/group/positron/repository/proposal.git">ssh://username@ifarml1/u/group/positron/repository/proposal.git</a></li>
<ol>
<li>Outside the firewall, you'll have to set up a tunnel</li>
<li>this will create a directory called "proposal" in the
directory that you executed the command</li>
</ol>
<li>cd proposal</li>
<li>make changes</li>
<li>git add newfile1.xxx newfile2.xxx</li>
<ol>
<li>"git add" adds new files to your copy of the repository<br>
</li>
</ol>
<li>git commit newfile1.xxx -m "new image for the summary
section"</li>
<li>git commit newfile2.xxx -m "another new image"</li>
<ol>
<li>Use this command to "commit" new files to your repository<br>
</li>
</ol>
<li>git commit -a -m "updated section 666 to reflect the actual
reality"</li>
<ol>
<li>this will commit all the existing files that have been
changed to your repository<br>
</li>
</ol>
<li>git push origin master</li>
<ol>
<li>This command actual pushes your changes back to JLAB
repository</li>
</ol>
</ol>
Note: git's strength is that everyone gets there own local copy
and all "git add" and "git commit" are held locally until the user
is ready to share his/her work. So please use git add and git
commit as much as possible. A firewall/network connect is only
needed for steps 1 & 8, so you can make use of git version
control even when not connected to the network.<br>
<br>
Working in an existing clone of repository the following
commands might be helpful:<br>
<ol>
<li>git pull</li>
<ol>
<li>will pull in and changes from the JLAB repository</li>
</ol>
<li>git status</li>
<ol>
<li>will give you the status of your local repository, any
changed or new files, this does not say anything about your
files and the repository</li>
</ol>
</ol>
I hope this is helpful. I'll work on a wiki page...let me know what
does and does not work.<br>
<br>
Arne<br>
<pre class="moz-signature" cols="72">--
Arne Freyberger
Director of Accelerator Operations
Jefferson Lab Office: (757) 269-6268
12000 Jefferson Avenue Cell: (757) 876-6289
Newport News, VA 23606 Email: <a class="moz-txt-link-abbreviated" href="mailto:freyberg@jlab.org">freyberg@jlab.org</a>
</pre>
</body>
</html>