[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

working from two machines

From: H.S. <hs.samix_at_gmail.com>
Date: Wed, 29 Oct 2008 19:57:52 -0400

Hello,

I am working on a project which I have hosted as a repository on our
university's network. The repository is on 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.). I just rsync from my lab machine to my home machine when I want
to work from home and then rsync back to update my lab machine. The
rsync command I use at home is this:
$> rsync -auCvze ssh ./ labmachine:~/project/

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
working copy in this situation.

What do others do in such a situation? Sorry if this is a basic
question. I am relatively new to SVN.

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 from home or lab in that unfinished state,
update my copy at home or lab and then continue working. Is this what is
commonly done in such situations?

Or perhaps there is way to rsync between two working copies while I am
working on an unfinished change?

Thanks,
Regards.

-- 
Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-30 00:58:37 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.