Hi, Ben.
Your solution is excellent! I've finally made it by the following
steps:
1. Create a bat file, which contains lines of commands:
svn propdel google:author file:///N:/svnroot2 --revprop -r 1
svn propdel google:author file:///N:/svnroot2 --revprop -r 2
svn propdel
On Fri, Jan 16, 2009 at 6:38 AM, Song1w evis...@gmail.com wrote:
Hi, Ben.
Your solution is excellent! I've finally made it by the following
steps:
1. Create a bat file, which contains lines of commands:
svn propdel google:author file:///N:/svnroot2 --revprop -r 1
svn propdel
You're quite right. ^_^
I think the loop command in Windows Command Prompt can be:
FOR /L %i IN (1,1,100) DO svn propdel google:author file:///N:/svnroot2
--revprop -r %i
On Jan 16, 9:26 pm, Ben Collins-Sussman suss...@google.com wrote:
On Fri, Jan 16, 2009 at 6:38 AM, Song1w
Dear Admin,
This issue is not solved yet, may I apply for another reset to this
repository(https://evis-blogenginedotnet.googlecode.com/svn/)?
I'll try again once it's reset. Thanks.
On Jan 8, 1:15 pm, Song1w evis...@gmail.com wrote:
Hi Daniel,
I re-did the sync operations and encountered
Song1w:
Does the source repository (in file:///N:/svnroot2) originally come
from googlecode as well?
On Thu, Jan 15, 2009 at 9:18 PM, Song1w evis...@gmail.com wrote:
Dear Admin,
This issue is not solved yet, may I apply for another reset to this
Hi Ben,
This file:///N:/svnroot2 is filtered from
https://siv-name.googlecode.com/svn/.
I did the following:
1. Use svnsync init and svnsync sync to synchronize the
https://siv-name.googlecode.com/svn/ with my local file:///N:/svnroot which
is just created.
2. Use *svnadmin dump*
I know what's going on -- it's a bug we just discovered, which I'm
fixing this week.
Specficially, whenever you do a commit to googlecode, the
'google:author' revision-property gets created by the server and
attached to the newly committed revision. This revprop is not
changeable, even by
Hi Daniel,
I re-did the sync operations and encountered another problem. Here is
the console output.
N:\svnsync init https://evis-blogenginedotnet.googlecode.com/svn/
file:///N:/svnroot2 --username EviSong
Copied properties for revision 0 (syn:sync-*
Done. Normally you should be able to manually continue your sync where
it left off when you receive an error such as this, so it may be worth
attempting if you encounter errors again.
As for the 502 errors, it's something we're looking in to.
Daniel
On Jan 7, 7:57 am, Song1w evis...@gmail.com
9 matches
Mail list logo
