This is not currently possible through 'rbt post'. If you wanted to review
the text free-form, you could copy it into a file and attach that to a
file attachment only review request. Review Board 2.0.x has nice support
for reviewing text file attachments.
-David
On Wed, Aug 27, 2014 at 11:00
Are there any errors in the Review Board log or the browser debug console?
-David
On Thu, Aug 28, 2014 at 6:09 AM, kovalyov...@gmail.com wrote:
I am using Reviewboard 2.0.6 with Postgres database in utf-8.
When I making new pre-commit request on svn-based repository with
diff-file
Read few posts about API Error 207, but still can't figure the problem with
my setup (this is a completely new RB installation for my company).
In the log below I replaced real path and file names with \a\b\c\d\e\f ...
I also verified that all svn commands shown in debug log work ok.
No luck.
Yes I did create a seperate site directory for the 1.7.27, called it
/var/www/review27, thats been deleted.
ran easy_install with the command line 'easy_install ReviewBoard==1.7.6'
then also ran 'rb-site install /var/www/reviewboard',
then tried 'easy_install
I'm confused. If you had a previous installation, why were you using
'rb-site install'? Upgrades should use 'rb-site upgrade'
If easy_install with == isn't changing the active version, you can try
deleting the 1.7.27 .egg directory from the python site-packages directory.
On Fri, Aug 29, 2014
I haven't seen this behavior. Note that the list of branches and the
commits are cached for a short period of time (5 minutes) in order to limit
the load on the server, so if you load the page, push, then immediately
reload, the new data may not show up.
-David
On Thu, Aug 28, 2014 at 5:21 AM,
Updates:
Status: Fixed
Comment #1 on issue 3547 by chip...@gmail.com: Display a sign-in dialog
when trying to post a comment for logged-out RB
https://code.google.com/p/reviewboard/issues/detail?id=3547
1.7.6 is really, really old. If your admin upgrades to a newer version,
this
Comment #1 on issue 3478 by kaptas.a...@gmail.com: Allow disabling Markdown
through an option/checkbox
https://code.google.com/p/reviewboard/issues/detail?id=3478
Same request here!
We often use ascii arts as ship it message.
This is my beautifull Dolly, and I cannot post her anymore :(
Status: New
Owner:
Labels: Type-Enhancement Priority-Medium
New issue 3548 by matt.yan...@gmail.com: Would like the ability to Like
or Thumbs up review comments.
https://code.google.com/p/reviewboard/issues/detail?id=3548
What version are you running?
2.0.6
What's the URL of the page
Updates:
Status: Fixed
Comment #3 on issue 3545 by trowb...@gmail.com: Review request shown in
list of wrong Subversion repository
https://code.google.com/p/reviewboard/issues/detail?id=3545
Fixed in release-2.0.x (44decb6). Thanks!
--
You received this message because this project
Comment #2 on issue 3135 by chip...@gmail.com: Support Assembla git
repositories
https://code.google.com/p/reviewboard/issues/detail?id=3135
This came up again. I opened a request with Assemblda:
https://groups.google.com/forum/#!topic/assembla-api-dev/9dgUfrlBEhA
--
You received this
Comment #2 on issue 3478 by trowb...@gmail.com: Allow disabling Markdown
through an option/checkbox
https://code.google.com/p/reviewboard/issues/detail?id=3478
If that isn't a critical use case I don't know what is.
--
You received this message because this project is configured to send all
Comment #3 on issue 3478 by chip...@gmail.com: Allow disabling Markdown
through an option/checkbox
https://code.google.com/p/reviewboard/issues/detail?id=3478
We will find a way to save your sheep!
At the very least, you should be able to prefix each line with 4 spaces, or
do something
13 matches
Mail list logo