Hi all, So, time to move the development of PyPy to http://codespeak.net/svn/pypy/trunk and keep http://codespeak.net/svn/pypy/dist for the latest known-stable copy of the trunk? Armin
Hi Armin, On Thu, Mar 29, 2007 at 14:13 +0200, Armin Rigo wrote:
yes - it was discussed yesterday on #pypy already a bit. There is the issue that the website/news come from dist but let this not prevent us from just doing the copy now. I also guess that nightly testing should shift to test 'trunk' regularly. holger
Hi Carl, On Thu, Mar 29, 2007 at 02:27:24PM +0200, Carl Friedrich Bolz wrote:
We should be careful to protect pypy-dist for accidental checkins, because otherwise we will certainly have accidents.
Is it possible to have a check-in hook that allows deletions and additions (possibly with history) within pypy/dist, but not changes? In this way we can only 'svn rm && svn cp' things to pypy/dist from some other place like pypy/trunk. Armin
Hi Armin, On Thu, Mar 29, 2007 at 14:13 +0200, Armin Rigo wrote:
yes - it was discussed yesterday on #pypy already a bit. There is the issue that the website/news come from dist but let this not prevent us from just doing the copy now. I also guess that nightly testing should shift to test 'trunk' regularly. holger
Hi Carl, On Thu, Mar 29, 2007 at 02:27:24PM +0200, Carl Friedrich Bolz wrote:
We should be careful to protect pypy-dist for accidental checkins, because otherwise we will certainly have accidents.
Is it possible to have a check-in hook that allows deletions and additions (possibly with history) within pypy/dist, but not changes? In this way we can only 'svn rm && svn cp' things to pypy/dist from some other place like pypy/trunk. Armin
participants (3)
-
Armin Rigo -
Carl Friedrich Bolz -
holger krekel