Re: Issue 2779 in reviewboard: Autocomplete enter key is not works in reviewers selection.

2013-06-11 Thread reviewboard


Comment #7 on issue 2779 by jimmyden...@gmail.com: Autocomplete enter key  
is not works in reviewers selection.

http://code.google.com/p/reviewboard/issues/detail?id=2779

How to buy cheap jerseys from china? I should like to commend our china  
jerseys paypal store to you. We professional Chinese Jerseys
wholesale,Great reputation and customer service,you will owning your  
favorite jerseys about 3-5 days ago.

http://www.lindajerseys.com china jerseys
http://www.lindajerseys.com/MLB-Jerseys-c94/   mlb jerseys
http://www.lindajerseys.com/NCAA-Jerseys-c118/ncaa jerseys
http://www.lindajerseys.com/NHL-Jerseys-c96/cheap nhl jerseys

--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Issue 3000 in reviewboard: UTF-8 support

2013-06-11 Thread reviewboard

Status: New
Owner: 
Labels: Type-Defect Priority-Medium

New issue 3000 by mechan...@gmail.com: UTF-8 support
http://code.google.com/p/reviewboard/issues/detail?id=3000

*** For customer support, please post to reviewbo...@googlegroups.com
*** If you have a patch, please submit it to
http://reviews.reviewboard.org/
***
*** Do not post confidential information in this bug report!

What version are you running?
1.7.7.

What's the URL of the page containing the problem?
Any field which can be filled by user

What steps will reproduce the problem?
1. Add any information containing non-Latin symbol, e.g. review title
2. Try to save this information

What is the expected output? What do you see instead?
The information is saved, because server default encoding is UTF-8
Actual result: I'm getting non-informative errors with error-code 0.

Further steps:
3. Check the encoding of the database used. It's Latin. I've converted the  
db to UTF-8 directly. I'm running MySQL, so I've used the following  
statements:

ALTER DATABASE `my_db` CHARACTER SET utf8 COLLATE utf8_general_ci;
4. I've reloaded the service, and repeated steps 1 and 2.
Expected result: I've got my non-Latin info saved, because the database  
encoding is now correct.
Actual result: I'm still getting Server-0 error, but my data is saved  
as ? ??.


5. I've set everywhere I could find UTF-8 in both MySQL.cnf, and  
reviewboard.py. No difference.


The solution was to create another site with DB initially created in UTF-8.  
After that my data is saved properly. In my point of view there are several  
fixing actions for my case (from most convenient to least):
a. make utf-8 the default encoding for gnu/linux systems (as already is in  
lots of other applications)
b. add info about utf-8 to the installation guide, like, now you should  
manually create the db... be aware that if you're planning to use non-Latin  
symbols, set the database encoding to utf-8
c. add this information to FAQ at your site -- I've found lots, and lots of  
similar requests in the Internet.

What operating system are you using? What browser?
Debian 6.0, MySQL 5.1. This issue is browser-independent.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Issue 3001 in reviewboard: Session cookies are stored imporperly

2013-06-11 Thread reviewboard

Status: New
Owner: 
Labels: Type-Defect Priority-Medium

New issue 3001 by mechan...@gmail.com: Session cookies are stored imporperly
http://code.google.com/p/reviewboard/issues/detail?id=3001

*** For customer support, please post to reviewbo...@googlegroups.com
*** If you have a patch, please submit it to
http://reviews.reviewboard.org/
***
*** Do not post confidential information in this bug report!

What version are you running?
1.7.7.1

What's the URL of the page containing the problem?
Review creation page

What steps will reproduce the problem?
1. Create user account for the reviewboard, login, stay logged in. Do not  
close the tab with session while doing all other steps

2. Add another user account, do not login
3. Change the database for the system.
3.1 I'm not sure if this is required, but wait for some time. In my case  
there was a week delay between sessions.

4. Return to the session created on step 1.
5. Create new review.
What is the expected output?
Session is expired, the system asks for login, and password
What do you see instead?
Review is created under another account. The IDs in database are probably  
the same, but content differs.


What operating system are you using? What browser?
Debian 6.0, MySQL 5.1, browser-independent issue

--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Issue 3002 in reviewboard: Some password is requied and valid when LDAP authentication is on

2013-06-11 Thread reviewboard

Status: New
Owner: 
Labels: Type-Defect Priority-Medium

New issue 3002 by mechan...@gmail.com: Some password is requied and valid  
when LDAP authentication is on

http://code.google.com/p/reviewboard/issues/detail?id=3002

*** For customer support, please post to reviewbo...@googlegroups.com
*** If you have a patch, please submit it to
http://reviews.reviewboard.org/
***
*** Do not post confidential information in this bug report!

What version are you running?
1.7.7.1

What's the URL of the page containing the problem?
admin/db/auth/user/add/

What steps will reproduce the problem?
1. In the admin/settings/authentication/ set LDAP authenticaton, fill all  
necessary fields, and save
2. In the admin/db/auth/user/add/ enter new username which is valid LDAP  
entity

3. Press the Save button

What is the expected output?
Since authentication is done through LDAP no pass..word should be entered  
-- admin knows nothing about user passwords

What do you see instead?
Password is required. Moreover, after user account is created one can login  
both under the entered AND LDAP password.


What operating system are you using? What browser?
Debian 6.0, MySQL 5.1, browser-independent issue.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Issue 3003 in reviewboard: Impossible to use nginx-apache proxy when running reviewboard

2013-06-11 Thread reviewboard

Status: New
Owner: 
Labels: Type-Defect Priority-Medium

New issue 3003 by mechan...@gmail.com: Impossible to use nginx-apache proxy  
when running reviewboard

http://code.google.com/p/reviewboard/issues/detail?id=3003

*** For customer support, please post to reviewbo...@googlegroups.com
*** If you have a patch, please submit it to
http://reviews.reviewboard.org/
***
*** Do not post confidential information in this bug report!

What version are you running?
1.7.7.1

What's the URL of the page containing the problem?
Any URL

What steps will reproduce the problem?
1. Create apache2 virtual host using provided master.
2. Create nginx virtual host which is proxy to the apache host
3. Use proxy_pass directive to apache, like, proxy_pass  
http://localhost:88;

4. Enable the host, open reviewboard, try to create the review

What is the expected output?
Review is created successfully. All links are modified in accordance with  
proxypass directive


What do you see instead?
One can login to the system, but review can not be created -- the requests  
are generated properly, but system responses are all wrong -- you generate  
the path from the beginning -- hostname in apache:port in apache/path,  
so the proxy modifications are ignored completely.
Though the proper behaviour is to create path starting from document root  
only leaving the hostname non-modified. That's the responsibility of  
web-server, not web-application.


What operating system are you using? What browser?
Debian 6.0, MySQL 5.1, browser-independent issue.

--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Issue 3004 in reviewboard: Unclear field names in LDAP authorization section

2013-06-11 Thread reviewboard

Status: New
Owner: 
Labels: Type-Defect Priority-Medium

New issue 3004 by mechan...@gmail.com: Unclear field names in LDAP  
authorization section

http://code.google.com/p/reviewboard/issues/detail?id=3004

*** For customer support, please post to reviewbo...@googlegroups.com
*** If you have a patch, please submit it to
http://reviews.reviewboard.org/
***
*** Do not post confidential information in this bug report!

What version are you running?
1.7.7.1

What's the URL of the page containing the problem?
admin/settings/authentication/

What steps will reproduce the problem?
1. In the upper part of the form unset the Allow anonymous read-only  
access mark

2. Go down the form filling ldap-related fields
3. Bump into the Anonymous User Mask, and Password.

What is the expected output?
I've expected the explanation who is this Anonymous, why he has a password  
(anonymity is always free), and why these fields are still active if I've  
already prohibited them to use my system

What do you see instead?
No clear info found. You've just retyped the settings below.

I'm using several other tools with LDAP auth, so I could guess what you  
mean. I suggest renaming these unclear setting to the following ones:


*
Manager DN  {instead of anonymous}
*

Help for this item:
*
If your LDAP server doesn't support anonymous binding (IOW, if your LDAP  
server doesn't even allow a query without authentication), then Jenkins  
would have to first authenticate itself against the LDAP server, and  
Jenkins does that by sending manager DN and password.


A DN typically looks like CN=MyUser,CN=Users,DC=mydomain,DC=com although  
the exact sequence of tokens depends on the LDAP server configuration. It  
can be any valid DN as long as LDAP allows this user to query data.


This configuration is also useful when you are connecting to Active  
Directory from a Unix machine, as AD doesn't allow anonymous bind by  
default. But if you can't figure this out, you can also change AD setting  
to allow anonymous bind. See this document for how to.

*
Or at least a part of this.

*
Manager Password
*
Explanation for this field:
*
Password for the manager DN specified above.
*

What operating system are you using? What browser?
Debian 6.0, MySQL 5.1, browser-independent issue.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Issue 3005 in reviewboard: timezone string limited to 20 char whereas some timezones are greater than 20

2013-06-11 Thread reviewboard

Status: New
Owner: 
Labels: Type-Defect Priority-Medium

New issue 3005 by nano...@gmail.com: timezone string limited to 20 char  
whereas some timezones are greater than 20

http://code.google.com/p/reviewboard/issues/detail?id=3005

*** For customer support, please post to reviewbo...@googlegroups.com
*** If you have a patch, please submit it to
http://reviews.reviewboard.org/
***
*** Do not post confidential information in this bug report!

What version are you running?
1.7.6 reviewboard server


What's the URL of the page containing the problem?
REVIEWBOARD_SERVER/account/preferences/


What steps will reproduce the problem?

1. change default timezone to America/Indiana/Indianapolis
2. no error reported but America/Indiana/Indi is saved in database
3. try to login and error 500 appears or try to change in admin section =
Ensure this value has at most 20 characters (it has 28)

What is the expected output? What do you see instead?

saved value should not be stripped = America/Indiana/Indianapolis


What operating system are you using? What browser?
any

timezone evolution adds a string fixed to 20 chars
https://github.com/reviewboard/reviewboard/blob/master/reviewboard/accounts/evolutions/timezone.py

AddField('Profile', 'timezone', models.CharField, initial=u'UTC',  
max_length=20)


it is also limited to 20 chars in model
https://github.com/reviewboard/reviewboard/blob/master/reviewboard/accounts/models.py

# Allows per-user timezone settings
timezone = models.CharField(choices=TIMEZONE_CHOICES, default='UTC',
max_length=20)

--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Issue 3005 in reviewboard: timezone string limited to 20 char whereas some timezones are greater than 20

2013-06-11 Thread reviewboard


Comment #1 on issue 3005 by nano...@gmail.com: timezone string limited to  
20 char whereas some timezones are greater than 20

http://code.google.com/p/reviewboard/issues/detail?id=3005

the biggest string length is 30 chars for America/Argentina/Buenos_Aires


import pytz
max=0
for tz in pytz.common_timezones:

... if len(tz)  max:
... max=len(tz)
... print %d %s % (len(tz), tz)
...
14 Africa/Abidjan
18 Africa/Addis_Ababa
20 Africa/Dar_es_Salaam
30 America/Argentina/Buenos_Aires


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Issue 3005 in reviewboard: timezone string limited to 20 char whereas some timezones are greater than 20

2013-06-11 Thread reviewboard


Comment #2 on issue 3005 by nano...@gmail.com: timezone string limited to  
20 char whereas some timezones are greater than 20

http://code.google.com/p/reviewboard/issues/detail?id=3005

I propose following change
http://reviews.reviewboard.org/r/4230

--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Issue 2999 in reviewboard: Tried to re-upload the screenshot after it became inaccessible.

2013-06-11 Thread reviewboard


Comment #2 on issue 2999 by vmx...@motorola.com: Tried to re-upload the  
screenshot after it became inaccessible.

http://code.google.com/p/reviewboard/issues/detail?id=2999

Review Board Revision 1.7.7.1

--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Issue 2999 in reviewboard: Tried to re-upload the screenshot after it became inaccessible.

2013-06-11 Thread reviewboard


Comment #3 on issue 2999 by vmx...@motorola.com: Tried to re-upload the  
screenshot after it became inaccessible.

http://code.google.com/p/reviewboard/issues/detail?id=2999

I'm wondering what a sysadmin might do that would prevent me from adding a  
new screenshot to an existing entry.  Review Board allowed me to delete the  
old entry, so why not allow me to add a new one?


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Issue 2999 in reviewboard: Tried to re-upload the screenshot after it became inaccessible.

2013-06-11 Thread reviewboard


Comment #4 on issue 2999 by trowb...@gmail.com: Tried to re-upload the  
screenshot after it became inaccessible.

http://code.google.com/p/reviewboard/issues/detail?id=2999

What do you mean by not allowed? Are you seeing an error message?


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Issue 2999 in reviewboard: Tried to re-upload the screenshot after it became inaccessible.

2013-06-11 Thread reviewboard


Comment #5 on issue 2999 by vmx...@motorola.com: Tried to re-upload the  
screenshot after it became inaccessible.

http://code.google.com/p/reviewboard/issues/detail?id=2999

Actually, I'm not even seeing a Screenshot section any more, as though it  
can only be added when the issue is opened.  So instead I tried to use  
Update  Add File.  Yesterday that failed without an error message (as I  
recall).  Today it works.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Issue 2999 in reviewboard: Tried to re-upload the screenshot after it became inaccessible.

2013-06-11 Thread reviewboard


Comment #6 on issue 2999 by trowb...@gmail.com: Tried to re-upload the  
screenshot after it became inaccessible.

http://code.google.com/p/reviewboard/issues/detail?id=2999

Ah yes, in 1.7.x, the screenshots are deprecated in favor of the more  
general file review UIs. If uploading files works as expected, then I'm  
tempted to say this isn't an issue.


There may still be something weird with the way your server is set up to  
store uploaded files, but you'll have to engage with whoever runs that  
server to debug that.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Issue 2999 in reviewboard: Tried to re-upload the screenshot after it became inaccessible.

2013-06-11 Thread reviewboard


Comment #7 on issue 2999 by vmx...@motorola.com: Tried to re-upload the  
screenshot after it became inaccessible.

http://code.google.com/p/reviewboard/issues/detail?id=2999

Please keep in mind that all of these issues transpired without my saying  
anything to the server administrator.  If it's working now then it went  
through a period of instability that would be difficult to account for by  
anything a system administrator would do.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Issue 2999 in reviewboard: Tried to re-upload the screenshot after it became inaccessible.

2013-06-11 Thread reviewboard


Comment #8 on issue 2999 by trowb...@gmail.com: Tried to re-upload the  
screenshot after it became inaccessible.

http://code.google.com/p/reviewboard/issues/detail?id=2999

There are plenty of things that might cause a period of instability with  
regards to file storage, such as momentary issues caused by upgrades or  
server maintenance, all the way to things like disk partitions filling up.


If you can find error messages either on your client or in the server logs,  
we can look into them, but we're pretty limited with the information you've  
given us so far.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Issue 3003 in reviewboard: Impossible to use nginx-apache proxy when running reviewboard

2013-06-11 Thread reviewboard

Updates:
Status: SetupIssue

Comment #1 on issue 3003 by trowb...@gmail.com: Impossible to use  
nginx-apache proxy when running reviewboard

http://code.google.com/p/reviewboard/issues/detail?id=3003

You can configure the server name in the admin settings. In this case, the  
web application *does* need to know the hostname, because it also sends out  
emails with links and provides fully-qualified URLs in the web API, and we  
don't make a distinction internally between the three different places that  
we generate URLs.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Issue 3001 in reviewboard: Session cookies are stored imporperly

2013-06-11 Thread reviewboard

Updates:
Status: NeedInfo

Comment #1 on issue 3001 by trowb...@gmail.com: Session cookies are stored  
imporperly

http://code.google.com/p/reviewboard/issues/detail?id=3001

I'm really not quite sure what you're reporting. Can you rephrase?

--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Issue 3000 in reviewboard: UTF-8 support is hard to enable

2013-06-11 Thread reviewboard

Updates:
Summary: UTF-8 support is hard to enable
Labels: Component-Docs

Comment #1 on issue 3000 by trowb...@gmail.com: UTF-8 support is hard to  
enable

http://code.google.com/p/reviewboard/issues/detail?id=3000

(No comment was entered for this change.)

--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.