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

Suggestions how to handle offline development on a notebook ?

From: Thilo Reichelt <Thilo.Reichelt_at_T-Online.de>
Date: 2005-05-01 22:25:54 CEST

Hi all,

does anybody has suggestions how to handle development on a notebook
with subversion?

We are 2 developers and sometimes a consultant or two plus a few people
who may change config files. We frequently have to change sw on the
customer site. The device in question may control heavy machinery, which
makes it very desirable to track all changes.
Up to now, I am the only one using subversion (or any other source
control). So for now, I just copy the whole repository to my laptop from
the server and back to the server on return.
Obviously, this procedure does not work any longer once my preachings to
use subversion have any effect, i.e. at least my full-time colleague
does switch to subversion. The probability of a conflict is really low
(we generally work on seperate areas) but not EXACTLY zero.

Does any body have a suggestion, which does meet the following requirements:

- Has a read-only full copy of the repository on the notebook (since I
may need older version or completely unrelated projects on site without
prior notice)
- Does keep the local history (Just checking in the on-site changes in a
single commit destroys to much information, sometimes failed attempts
are very informative)
- Does work with file:// on an FSFS repository (The servers here are
Novell Netware, and if I need a different server, I have to maintain it
myself including backup)

Would the following process work?
- make copy inside the repository from <repostory>/project to
<repostory>/<developer>_notebook/project
- copy the repository to the notebook
- commit all work on the notebook to
<repostory>/<developer>_notebook/project
- back at the desk, do svnadmin dump <repostory>/<developer>_notebook
and then svnadmin load --parent-dir <developer>_notebook
- merge trunk and <developer>_notebook into trunk
- empty everything in <developer>_notebook so that the whole thing works
again next time
- copy the repository from the server to the notebook

As I said, conflicts are highly unlikely. So in most cases, subversion
could do the merge automatically.

I have read about SVK, but I need a solution which works similar on the
notebook and the desktop. The people I am trying to get to use
subversion have never before heard of version control.

Any comments or suggestions?

Thanks
Thilo Reichelt

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 2 06:50:17 2005

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