Martin v. Löwis schrieb:
> Thomas Heller wrote:
>> - Do I need special rights to call 'svnadmin load' to import this dumpfile
>> into Python SVN, or are the normal commit rights sufficient?
>
> It's called "svnadmin" for a reason :-)
>
> Neal Norwitz or myself will have to do that; we need to d
Martin v. Löwis schrieb:
> Thomas Heller wrote:
>> - Do I need special rights to call 'svnadmin load' to import this dumpfile
>> into Python SVN, or are the normal commit rights sufficient?
>
> It's called "svnadmin" for a reason :-)
>
> Neal Norwitz or myself will have to do that; we need to d
Thomas Heller wrote:
> - Do I need special rights to call 'svnadmin load' to import this dumpfile
> into Python SVN, or are the normal commit rights sufficient?
It's called "svnadmin" for a reason :-)
Neal Norwitz or myself will have to do that; we need to do it on the
repository machine locall
Martin v. Löwis schrieb:
> Thomas Heller wrote:
>> What I did was at a certain time develop in the 'branch_1_0' branch, leaving
>> HEAD for experimental work. Later I decided that this was wrong, cvs
>> removed all
>> files in HEAD, and added them back from a branch_1_0 checkout. Maybe doing
>>
Thomas Heller wrote:
> Is it possible to take the CVS repository files (they can be accessed
> with rsync), and import that, preserving the whole history, into SVN?
Yes:
http://cvs2svn.tigris.org/
You just need a maintainer of the Python SVN repository to load the dump
files this tool generates.
Thomas Heller wrote:
> What I did was at a certain time develop in the 'branch_1_0' branch, leaving
> HEAD for experimental work. Later I decided that this was wrong, cvs removed
> all
> files in HEAD, and added them back from a branch_1_0 checkout. Maybe doing
> this was another bad idea, as th
>> I think the best would be to import it into an url like
>>
>> http://svn.python.org/projects/sandbox/trunk/ctypes/
>>
>> Is it possible to take the CVS repository files (they can be accessed
>> with rsync), and import that, preserving the whole history, into SVN?
>
Gustavo Niemeyer schrieb:
> I think the best would be to import it into an url like
>
> http://svn.python.org/projects/sandbox/trunk/ctypes/
>
> Is it possible to take the CVS repository files (they can be accessed
> with rsync), and import that, preserving the whole history, into SVN?
It should be possible to use cvs2s
On 6/23/06, Thomas Heller <[EMAIL PROTECTED]> wrote:
Is it possible to take the CVS repository files (they can be accessedwith rsync), and import that, preserving the whole history, into SVN?I don't remember a svn-specific tool for it (although I am fairly out of touch in that regard). However, if
Now that ctypes is no longer an externally maintained module, imo the
repository should be moved from SF cvs to python.org svn.
The current layout is different than the main python trunk, and it
should be preserved so that I can still do standalone releases.
I think the best would be to import
10 matches
Mail list logo
