RE: Is SVN ready for use?

On Mon, 2002-12-09 at 16:01, Roman Rytov wrote:
>
>

> >
> > -garrett
>
> That what watch and editors commands stand in CVS for. I didn't mean
> that lack of such commands is insurmountable obstacle but it's like
> safety measure. If it is it's better.
>
> RR
>

Roman,

        For what it's worth, at my shop, we CVS, and don't use watch/edit (we
want to move to SVN when it's version 1.0). We setup commit messages to
go out to all the developers. Personally, I use a task scheduler (cron)
to go find all my working copies and run cvs diff relative to the
current production install tag at the top of each repository.

        It also tar's up all files in the working copy and attaches them as a
tar file. I use it as a poor man's distributed repository. If I lose
my development branch before I commit, I've always got it "committed" to
my e-mail spool. I blow away old copies about once a quarter.

        The diff's (mine and the commit logs version), serve as a reminder of
what is outstanding I need to do an update for, and what I have local
that needs to be checked in. This is the system I've worked out that
works well for me.

        I'm in the habit of using cvs update/diff/commit regularly, but the
above should help to stand in kinda sort for edit/watch, and remind
developers what they need to check in.

        Thanks,
                Kirby

> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>

-- 
Real Programmers view electronic multimedia files with a hex editor.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org