-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 14 February 2002 07:42 am, you wrote:
> > > Sure, this is easy to do with any SCM system, as long as the system
> > > has 'post-commit' hooks. Subversion's own repository has a
> > > post-commit hook script that mails out a unified diff of the commit's
> > > changes to all svn developers. You could tweak that script to apply
> > > the very same diff to a CVS working copy and run 'cvs commit'. It's a
> > > no-brainer.
...
> I don't understand: why do you think you need a module? Is there
> something insufficient about the solution I described above?
...
> * whenever you commit to Subversion, a post-commit hook script
> patches your CVS working copy and commits the changes to the
> Sourceforge repo.
This is slightly off the direction this thread is going, but I'm not sure
that this would be a no-brainer.
How would you deal with mv and cp without losing history in the CVS
repository, for instance?
- --
|.. I'll never forget the first time I ran Windows, but I'm trying...
<|>
/|\
/|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8a+UzP0KxygnleI8RAptjAJ4+ofwst09Yk5sBb9V1Ve3Z9Er5FgCgzEmf
CPQQbnf2kb55QRyiuVSf+YA=
=oLL+
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:07 2006