public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aaron Walker <ka0ttic@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] GLEP 36: providing both CVS and Subversion?
Date: Sun, 10 Apr 2005 12:39:45 -0400	[thread overview]
Message-ID: <425956D1.5040006@gentoo.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Regarding GLEP 36[1], solar has asked me to try and figure out a way to provide
both CVS and Subversion for one repository and keep them sync'd somehow.

Although this was not the intention of my glep, it would be nice to get this
implemented, as it means all developers of a certain project would not be
forced to use one over the other.

Unfortunately, I have almost zero experience with repository administration
(CVS or Subversion), so I'm writing this with hopes that some of you guys have
some ideas.

The only idea I've had is to maybe setup post-commit hooks for both that commit
what was just committed to the other (cvs post-commit commits the stuff to svn
and vice versa).  Is this possible?

Cheers

[1] http://www.gentoo.org/proj/en/glep/glep-0036.html
- --
Bork Bork Bork!

Aaron Walker <ka0ttic@gentoo.org>
[ BSD | cron | forensics | shell-tools | commonbox | netmon | vim | web-apps ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCWVbRC3poscuANHARAvxuAJoDb2zpGYUxnPqYrT0gIjrNOlr1sACgrC9V
rrLF/g1JKTsV7kCsJcj6J0I=
=hpQB
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2005-04-10 16:39 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-10 16:39 Aaron Walker [this message]
2005-04-10 17:12 ` [gentoo-dev] GLEP 36: providing both CVS and Subversion? Ciaran McCreesh
2005-04-10 17:27   ` Patrick Lauer
2005-04-10 17:32     ` Ciaran McCreesh
2005-04-10 17:47       ` Christian Parpart
2005-04-10 17:44     ` Christian Parpart
2005-04-10 17:53       ` Ciaran McCreesh
2005-04-10 18:27         ` Christian Parpart
2005-04-10 18:34           ` Ciaran McCreesh
2005-04-10 21:57             ` Christian Parpart
2005-04-11  6:26               ` Ciaran McCreesh
2005-04-11 20:23                 ` Christian Parpart
2005-04-11 20:42                   ` Ciaran McCreesh
2005-04-11 21:32                     ` Christian Parpart
2005-04-12 18:50                     ` Paul de Vrieze
2005-04-12 18:57                       ` Ciaran McCreesh
2005-04-13  1:33                         ` Christian Parpart
2005-04-13  6:26                           ` Ciaran McCreesh
2005-04-13 13:03                             ` Aaron Walker
2005-04-13 14:46                               ` Christian Parpart
2005-04-10 18:14 ` Lance Albertson
2005-04-10 18:23   ` Ciaran McCreesh
2005-04-10 21:30   ` Daniel Drake
2005-04-10 21:35     ` Greg KH
2005-04-10 21:44       ` Christian Parpart
2005-04-10 22:08         ` Daniel Drake
2005-04-10 21:48       ` Patrick Lauer
2005-04-10 22:00         ` Lance Albertson
2005-04-10 22:20       ` Donnie Berkholz
2005-04-12 23:22     ` Nicholas Jones
2005-04-12 18:31 ` Paul de Vrieze

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=425956D1.5040006@gentoo.org \
    --to=ka0ttic@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox