[PEPPo] attempt at a repository

[Arne Freyberger]

eric,
try it now, I've made it wide open in terms of permissions, we can 
tighten it down later once we work through the issues.
Arne

On 06/10/2011 09:01 AM, Eric Voutier wrote:
>   Hello Arne,
>
>   I try the 1st step from ifarml1 but does not work for me. I assume 
> that I am not part of the positron
>   group which is consistent with what I see when I issue a "groups" 
> command and the fact that I dont
>   see a directory under my name when I scan the positron directory.
>   Joe, are you taking care of this or whom should I ask to be added ?
>
>    Eric
>
> Le 01/06/2011 18:37, Arne Freyberger a écrit :
>> Eric and Alex,
>>     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.
>>
>> Here is how to get latest version of the proposal (assuming linux 
>> command prompt):
>>
>>    1. git clone
>>       ssh://username@ifarml1/u/group/positron/repository/proposal.git
>>          1. Outside the firewall, you'll have to set up a tunnel
>>          2. this will create a directory called "proposal" in the
>>             directory that you executed the command
>>    2. cd proposal
>>    3. make changes
>>    4. git add newfile1.xxx newfile2.xxx
>>          1. "git add" adds new files to  your copy of the repository
>>    5. git commit  newfile1.xxx -m "new image for the summary section"
>>    6. git commit  newfile2.xxx -m "another new image"
>>          1. Use this command  to "commit" new files to your repository
>>    7. git commit -a -m "updated section 666 to reflect the actual
>>       reality"
>>          1. this will commit all the existing files that have been
>>             changed to your repository
>>    8. git push origin master
>>          1. This command actual pushes your changes back to JLAB
>>             repository
>>
>> 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.
>>
>>     Working in an existing clone of repository the following commands 
>> might be helpful:
>>
>>    1. git pull
>>          1. will pull in and changes from the JLAB repository
>>    2. git status
>>          1. 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
>>
>> I hope this is helpful.  I'll work on a wiki page...let me know what 
>> does and does not work.
>>
>> Arne
>> -- 
>> Arne Freyberger
>> Director of Accelerator Operations
>> Jefferson Lab           Office: (757) 269-6268
>> 12000 Jefferson Avenue  Cell:   (757) 876-6289
>> Newport News, VA 23606  Email:freyberg at jlab.org
>>
>>
>> _______________________________________________
>> PEPPo mailing list
>> PEPPo at jlab.org
>> https://mailman.jlab.org/mailman/listinfo/peppo
>
>
> _______________________________________________
> PEPPo mailing list
> PEPPo at jlab.org
> https://mailman.jlab.org/mailman/listinfo/peppo

-- 
Arne Freyberger
Director of Accelerator Operations
Jefferson Lab           Office: (757) 269-6268
12000 Jefferson Avenue  Cell:   (757) 876-6289
Newport News, VA 23606  Email:  freyberg at jlab.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://mailman.jlab.org/pipermail/peppo/attachments/20110610/46f69237/attachment.html