Comment #3 on issue 3312 by george.m...@gmail.com: Diffs without embedded
commit IDs can not be used
http://code.google.com/p/reviewboard/issues/detail?id=3312
Just tried to use rbt post which failed too, but maybe this is a separate
issue:
Comment #5 on issue 3376 by nicolas@gmail.com: RBTools 0.6 -
UnicodeEncodeError with ISO-8859-15
http://code.google.com/p/reviewboard/issues/detail?id=3376
Hello,
No, the issue is not causing only by this diff file. We have several others
which generate the same error.
As you can
Comment #6 on issue 3329 by thom.ger...@gmail.com: Show proper error
message when attempting to publish review request with duplicate commit ID
http://code.google.com/p/reviewboard/issues/detail?id=3329
Seeing this in deployed Reviewboard 2.0.1 with a MySQL db. user doing
PUT
Comment #6 on issue 3376 by trowb...@gmail.com: RBTools 0.6 -
UnicodeEncodeError with ISO-8859-15
http://code.google.com/p/reviewboard/issues/detail?id=3376
Does this particular .diff file produce the exact same text in the Error
data part of the traceback?
--
You received this message
Comment #7 on issue 3329 by trowb...@gmail.com: Show proper error message
when attempting to publish review request with duplicate commit ID
http://code.google.com/p/reviewboard/issues/detail?id=3329
I think that yours is a separate bug. Would you mind filing it, and
including the stack
Updates:
Status: PendingReview
Owner: trowb...@gmail.com
Labels: Component-RBTools
Comment #1 on issue 3410 by trowb...@gmail.com: perforce post-submit review
fails using rbt post when the submitted change set contains branch actions
Comment #5 on issue 3356 by trowb...@gmail.com: Diff currently
unavailable when reviewing change to file that is not pushed to remote
repo yet
http://code.google.com/p/reviewboard/issues/detail?id=3356
So the diffs there look correct--it's generating a diff between def456 and
abc123 (the
Updates:
Status: ThirdParty
Comment #8 on issue 3354 by trowb...@gmail.com: TypeError for New Review
Request and View Diff after updade to Review Board 2.0
http://code.google.com/p/reviewboard/issues/detail?id=3354
This traceback is nonsense, and I can't even find ConfigItem used in
Comment #8 on issue 2184 by bruce.c...@gmail.com: Mercurial rename support:
Pure file renames with *no actual changes* to the file fails with Diff did
not apply cleanly
http://code.google.com/p/reviewboard/issues/detail?id=2184
I came across this problem today: the problem is that patch
Updates:
Status: ThirdParty
Comment #9 on issue 2184 by trowb...@gmail.com: Mercurial rename support:
Pure file renames with *no actual changes* to the file fails with Diff did
not apply cleanly
http://code.google.com/p/reviewboard/issues/detail?id=2184
That sounds like great news.
Updates:
Status: NeedInfo
Comment #1 on issue 3409 by trowb...@gmail.com: List of which commits that
are reviewed/not reviewed
http://code.google.com/p/reviewboard/issues/detail?id=3409
If you're using the new post-commit UI in 2.0, you should see an icon next
to all commits that
11 matches
Mail list logo