CVS caching/offline commits

[Edward Glowacki]

Quoted from Ben Pfaff on Fri, Sep 28, 2001 at 02:31:37PM -0700:
> Edward Glowacki <glowack2@msu.edu> writes:
> 
> > Does CVS allow you to work offline?  Yes, I know you can edit files
> > without a net connection, you know that's not what I mean... ;)
> 
> Not AFAIK.
> 
> > Granted, for major projects this might be a bit, um, precarious, but for
> > small setups (like editing personal web pages or something), it would
> > seem that this might be possible.  Any thoughts?
> 
> Personally I just make a backup of the whole source tree at each
> stage with `tar cfz' or `cp -a'.

Then what, do you untar and "cvs commit" each one sequentially?
Or just use the tarballs as backup and only check in the final
version when you're done?

The whole problem really relates to trying to keep things in sync
between my laptop and a presumably safer server (or servers).  The
catch is that some things require different methods of storing
data.  For tracking version changes in source code or web pages,
CVS is good.  For other things like copies of online documentation
(Python, docbook, wxwindows, etc.), rsync is probably a better
choice.  Then there's the whole offline issue to solve so that it's
easy to sync all things that have been changed and queued.  

"I still haven't found what I'm looking for."


-- 
Edward Glowacki				glowack2@msu.edu
GLLUG Peon  				http://www.gllug.org
Imagination is the one weapon in the war against reality.
                -- Jules de Gaultier