CVS caching/offline commits
Bennett, Daniel
daniel.bennett@jnli.com
Tue, 2 Oct 2001 09:24:30 -0400
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C14B45.91267D90
Content-Type: text/plain;
charset="iso-8859-1"
What about putting the CVS repository on a CODA filesystem?
-----Original Message-----
From: Edward Glowacki [mailto:glowack2@msu.edu]
Sent: Tuesday, October 02, 2001 9:18 AM
To: Linux User's Group
Subject: Re: CVS caching/offline commits
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
_______________________________________________
linux-user mailing list
linux-user@egr.msu.edu
http://www.egr.msu.edu/mailman/listinfo/linux-user
------_=_NextPart_001_01C14B45.91267D90
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.45">
<TITLE>RE: CVS caching/offline commits</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>What about putting the CVS repository on a CODA =
filesystem?</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Edward Glowacki [<A =
HREF=3D"mailto:glowack2@msu.edu">mailto:glowack2@msu.edu</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, October 02, 2001 9:18 AM</FONT>
<BR><FONT SIZE=3D2>To: Linux User's Group</FONT>
<BR><FONT SIZE=3D2>Subject: Re: CVS caching/offline commits</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Quoted from Ben Pfaff on Fri, Sep 28, 2001 at =
02:31:37PM -0700:</FONT>
<BR><FONT SIZE=3D2>> Edward Glowacki <glowack2@msu.edu> =
writes:</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> > Does CVS allow you to work offline? =
Yes, I know you can edit files</FONT>
<BR><FONT SIZE=3D2>> > without a net connection, you know that's =
not what I mean... ;)</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Not AFAIK.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> > Granted, for major projects this might be =
a bit, um, precarious, but for</FONT>
<BR><FONT SIZE=3D2>> > small setups (like editing personal web =
pages or something), it would</FONT>
<BR><FONT SIZE=3D2>> > seem that this might be possible. =
Any thoughts?</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Personally I just make a backup of the whole =
source tree at each</FONT>
<BR><FONT SIZE=3D2>> stage with `tar cfz' or `cp -a'.</FONT>
</P>
<P><FONT SIZE=3D2>Then what, do you untar and "cvs commit" =
each one sequentially?</FONT>
<BR><FONT SIZE=3D2>Or just use the tarballs as backup and only check in =
the final</FONT>
<BR><FONT SIZE=3D2>version when you're done?</FONT>
</P>
<P><FONT SIZE=3D2>The whole problem really relates to trying to keep =
things in sync</FONT>
<BR><FONT SIZE=3D2>between my laptop and a presumably safer server (or =
servers). The</FONT>
<BR><FONT SIZE=3D2>catch is that some things require different methods =
of storing</FONT>
<BR><FONT SIZE=3D2>data. For tracking version changes in source =
code or web pages,</FONT>
<BR><FONT SIZE=3D2>CVS is good. For other things like copies of =
online documentation</FONT>
<BR><FONT SIZE=3D2>(Python, docbook, wxwindows, etc.), rsync is =
probably a better</FONT>
<BR><FONT SIZE=3D2>choice. Then there's the whole offline issue =
to solve so that it's</FONT>
<BR><FONT SIZE=3D2>easy to sync all things that have been changed and =
queued. </FONT>
</P>
<P><FONT SIZE=3D2>"I still haven't found what I'm looking =
for."</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>Edward Glowacki =
=
=
glowack2@msu.edu</FONT>
<BR><FONT SIZE=3D2>GLLUG Peon =
=
=
<A =
HREF=3D"http://www.gllug.org" =
TARGET=3D"_blank">http://www.gllug.org</A></FONT>
<BR><FONT SIZE=3D2>Imagination is the one weapon in the war against =
reality.</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; -- Jules de Gaultier</FONT>
</P>
<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>linux-user mailing list</FONT>
<BR><FONT SIZE=3D2>linux-user@egr.msu.edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://www.egr.msu.edu/mailman/listinfo/linux-user" =
TARGET=3D"_blank">http://www.egr.msu.edu/mailman/listinfo/linux-user</A>=
</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C14B45.91267D90--