Hi Arjun,
I'm on the road and don't have the URL handy, but if you'll go through
the archive for the past couple days you'll see a thread on exactly
this. Can you try the tests and workarounds in there and reply to that
thread with the requested info?
Christian
On Saturday, January 29, 2011, Arj
Hi,
Everything related to cvs checkout was working on reviewboard version
1.5, we migrated to the latest version 1.5.2 and cvs checkouts failed.
The rbssh command line failed to the error was shown as "repository
not found in path".
What needs to be fixed in rbssh for it to make cvs checkouts wo
Okay, that sounds great :-) Thanks for looking in to this!
--Noah
"Christian Hammond" wrote:
>I'm putting in a fix that checks for .git/svn. Even if it's empty, you
>should be able to just nuke it and then never deal with it again. We'll
>no
>longer run 'git svn info' unless we see it.
>
>I'd r
On 2011-01-29 4:03, Christian Hammond wrote:
Hi Scott,
The ordering is, I believe, based on the name. Changing the name
shouldn't invalidate anything, as we key things based on the
repository's numeric ID.
I changed the name of my least-used repository, and it did correctly
change the orderi
I'm putting in a fix that checks for .git/svn. Even if it's empty, you
should be able to just nuke it and then never deal with it again. We'll no
longer run 'git svn info' unless we see it.
I'd rather not go the route of checking the contents just yet, as it's
possible we'll break some legitimate
Hi Praveen,
The "root:" part you're seeing is just from the logging.
To be sure, are you able to ping that hostname from the server? What happens
if you try to ssh to it directly? If that works, what happens if you try
with rbssh? That might help narrow it down, because at the point where it's
fa
Hi Scott,
The ordering is, I believe, based on the name. Changing the name
shouldn't invalidate anything, as we key things based on the
repository's numeric ID.
There's nothing for changing the default order. There are feature
requests filed asking to pre-select a default for a user based on what
