Re: [Python-Dev] r42015 - peps/trunk

David Goodger wrote: > On 1/12/06, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: >> I know, but I wouldn't expect SVN to query other servers >> than svn.python.org inside the standard repository >> directories. >> >> AFAIK, this is a first in the Python repository. > > True, and worth discussing. Luck

Re: [Python-Dev] r42015 - peps/trunk

> [David Goodger] >> An alternative is to use svn:externals to link to a specific >> revision (via the -r option); [Tim Peters] > Yes. please. Done. -- David Goodger signature.asc Description: OpenPGP digital signature

Re: [Python-Dev] r42015 - peps/trunk

[Tim Peters] >> Yes. please. svn:externals should always pin to a specific revision >> (or at least to a "frozen" tag). Updating to a new revision then is >> just a propedit away (to change the revision number); ditto for >> backing off to an older revision if the newer one has problems. [Fredri

Re: [Python-Dev] r42015 - peps/trunk

[David Goodger] ... > An alternative is to use svn:externals to link to a specific > revision (via the -r option); Yes. please. svn:externals should always pin to a specific revision (or at least to a "frozen" tag). Updating to a new revision then is just a propedit away (to change the revision

Re: [Python-Dev] r42015 - peps/trunk

Tim Peters wrote: > Yes. please. svn:externals should always pin to a specific revision > (or at least to a "frozen" tag). Updating to a new revision then is > just a propedit away (to change the revision number); ditto for > backing off to an older revision if the newer one has problems. wasn'

Re: [Python-Dev] r42015 - peps/trunk

On 1/12/06, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: > I know, but I wouldn't expect SVN to query other servers > than svn.python.org inside the standard repository > directories. > > AFAIK, this is a first in the Python repository. True, and worth discussing. Luckily the PEPs repository is a low

Re: [Python-Dev] r42015 - peps/trunk

M.-A. Lemburg wrote: > AFAIK, this is a first in the Python repository. Not > sure if it's such a good idea. Branching and tagging > doesn't work with external resources in Subversion, > so things can become inconsistent. > > Also, what if you break the code in the berlios repo > or the server is

Re: [Python-Dev] r42015 - peps/trunk

David Goodger wrote: > On 1/12/06, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: >> Hmm, shouldn't these things be tracked under external/ ?! > > What do you mean exactly? A new "external" directory? Yes. > SVN provides a built-in mechanism for tracking external > repositories, via the "svn:externals

Re: [Python-Dev] r42015 - peps/trunk

On 1/12/06, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: > Hmm, shouldn't these things be tracked under external/ ?! What do you mean exactly? A new "external" directory? SVN provides a built-in mechanism for tracking external repositories, via the "svn:externals" property, and that's what I used. -

Re: [Python-Dev] r42015 - peps/trunk

David Goodger wrote: > [M.-A. Lemburg] >> Question: why do we need docutils in the peps/trunk/ directory >> in the first place ? > > It's a convenience, so that a separate Docutils download & install > (& maintain) isn't necessary for those who process reST-format PEPs. Hmm, shouldn't these thing

Re: [Python-Dev] r42015 - peps/trunk

[M.-A. Lemburg] > Question: why do we need docutils in the peps/trunk/ directory > in the first place ? It's a convenience, so that a separate Docutils download & install (& maintain) isn't necessary for those who process reST-format PEPs. -- David Goodger signatu

Re: [Python-Dev] r42015 - peps/trunk

David Goodger wrote: >> Author: david.goodger >> Date: Thu Jan 12 04:33:16 2006 >> New Revision: 42015 >> >> Modified: >>peps/trunk/ (props changed) >> Log: >> add external link to Docutils public repo -- always up-to-date > > I just deleted the static copy of the "docutils" directory from t

Re: [Python-Dev] r42015 - peps/trunk

> Author: david.goodger > Date: Thu Jan 12 04:33:16 2006 > New Revision: 42015 > > Modified: >peps/trunk/ (props changed) > Log: > add external link to Docutils public repo -- always up-to-date I just deleted the static copy of the "docutils" directory from the "peps" repository, and added