Updates:
Status: Fixed
Owner: chip...@gmail.com
Comment #4 on issue 3170 by chip...@gmail.com: RBTools: A critical bug for
handling P4Proxy
http://code.google.com/p/reviewboard/issues/detail?id=3170
This was fixed in 0.5.3.
--
You received this message because this project is
Comment #3 on issue 3170 by chip...@gmail.com: RBTools: A critical bug for
handling P4Proxy
http://code.google.com/p/reviewboard/issues/detail?id=3170
Apply this patch and see if things work better.
Attachments:
0001-Add-the-requested-hostname-to-the-Perforce-repo-path.patch 2.2 KB
Comment #2 on issue 3170 by chip...@gmail.com: RBTools: A critical bug for
handling P4Proxy
http://code.google.com/p/reviewboard/issues/detail?id=3170
Actually, let me get you a more detailed patch to try.
--
You received this message because this project is configured to send all
issue no
Updates:
Status: NeedInfo
Labels: Component-RBTools
Comment #1 on issue 3170 by chip...@gmail.com: RBTools: A critical bug for
handling P4Proxy
http://code.google.com/p/reviewboard/issues/detail?id=3170
We can't delete that code, as other companies depend on it, but what we
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 3170 by eyuw...@gmail.com: RBTools: A critical bug for handling
P4Proxy
http://code.google.com/p/reviewboard/issues/detail?id=3170
What version are you running?
RBTools 0.5.2
We have multiple sites in our company where eac
