Re: working with svn copy on two machines

2008-11-02 Thread H.S.
oneman wrote: > > On 2-nov-2008, at 11:24, John Allen wrote: >>> >> Yes. Do not use rsync. Only use svn, and commit after working, and >> update on the other machine to get the changes. > > Or, if you don't like having a gazillion intermediate commits in your > trunk, you could also create a bran

Re: working with svn copy on two machines

2008-11-02 Thread oneman
On 2-nov-2008, at 11:24, John Allen wrote: H.S. wrote: I am trying to see if there is a way such that I can use both my lab machine and home machine copies of the source code as working copies. The way I understand is that when I am in the middle of some change, I will have to commit back

Re: working with svn copy on two machines

2008-11-02 Thread John Allen
H.S. wrote: Hello, I am working on a project which I have hosted as a repository on our university's network. The repository is in my home directory. Now, I either work in my lab at the univ. or from home. Till now I have been using my univ. computer only for svn commands (update, commit, etc.)

Re: working with svn copy on two machines

2008-10-30 Thread Kamaraju S Kusumanchi
H.S. wrote: > The > rsync command I use at home is this: > $> rsync -auCvze ssh ./ labmachine:~/project/ I use $ rsync -avzp source destination > > However, this way I cannot give svn commands at my home machine. It > would be nice to do so though. Basically, only my lab machine is the > wor

working with svn copy on two machines

2008-10-30 Thread H.S.
Hello, I am working on a project which I have hosted as a repository on our university's network. The repository is in my home directory. Now, I either work in my lab at the univ. or from home. Till now I have been using my univ. computer only for svn commands (update, commit, etc.) where I had c