Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-07-28 Thread Barry Warsaw
On Thu, 2005-07-28 at 22:59, Tim Peters wrote: Yup, me too -- between the two of us, we don't have enough fingers to count how many trunks, branches, and tags of ZODB and Zope I have to fiddle with. I have a small inkling of your pain. They're all still copy, paste, tail-edit for me, and--

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-07-28 Thread Martin v. Löwis
Barry Warsaw wrote: I know that SF has promised svn access to projects for a long time now, but I haven't heard anything from them in a long time. It's listed under their Strategic Projects but the last update to that news item was back in April. Question: do we wait for SF to make the

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-07-28 Thread Fred L. Drake, Jr.
On Thursday 28 July 2005 20:07, Fernando Perez wrote: or something similar. It's an extra few chars, and it would give a convenient way to branch off pieces of the main code into their own subprojects in the future if needed. More interestingly, keeping it in a single repository makes it

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-07-28 Thread Martin v. Löwis
Tony Meyer wrote: Is there any reason that this should be an option, and not just done? Certainly: it's administrator load, which in turn is volunteer time. For occasional source (particularly C source) lookups, I've found webcvs really useful (especially when on a machine without cvs or

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-07-28 Thread Christopher Petrilli
On 7/29/05, Fred L. Drake, Jr. [EMAIL PROTECTED] wrote: On Thursday 28 July 2005 20:07, Fernando Perez wrote: or something similar. It's an extra few chars, and it would give a convenient way to branch off pieces of the main code into their own subprojects in the future if needed.

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-07-28 Thread Martin v. Löwis
Fred L. Drake, Jr. wrote: More interestingly, keeping it in a single repository makes it easier to merge projects, or parts of projects, together, without losing the history. This would be useful when developing packages that may be considered for the standard library, but which also

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-07-28 Thread Martin v. Löwis
Barry Warsaw wrote: We won't use plain text, but we may (or, we currently do) use basic auth over ssl. The security then is in the passwords, so we have to make sure they're generated securely. That (sort of) *is* plain text passwords. Somebody who took over svn.python.org can get the

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-07-28 Thread Martin v. Löwis
Tim Peters wrote: Ah, before I forget, single repository has worked very well for Zope (which includes top-level Zope2, Zope3, ZODB, ZConfig, zdaemon, ... projects): http://svn.zope.org/ Long URLs don't really get in the way in practice (rarely a need to type one after initial

<    1   2