Bug 609077 - git-svn cannot deal with charset or encoding of svn log.
Summary: git-svn cannot deal with charset or encoding of svn log.
Status: CLOSED WONTFIX
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: git   
(Show other bugs)
Version: el5
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Chris Wright
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-29 11:34 UTC by Kirby Zhou
Modified: 2016-06-24 10:27 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-06-24 10:27:53 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Kirby Zhou 2010-06-29 11:34:29 UTC
Description of problem:

git-svn cannot deal with charset or encoding of svn log.

Svn always store log message in utf-8 format, bug git-svn do not convert it into current locale.

For example, I do 'git-svn clone ...' with LC_CTYPE=zh_CN.gbk, then do 'git-svn log' to watch the log'. What can I see, just a lot of unreadable codes.

I have tested git-1.6.6.1, it can convert log into gbk with LC_CTYPE=zh_CN.gbk while cloning, it sounds much better than 1.5.5.6. But If I swith to LC_CTYPE=zh_CN.utf-8 sometime later, 'git-svn log' still returns gbk encoded text, it is illformed.


Version-Release number of selected component (if applicable):

1.5.5.6-4.el5

How reproducible:

Comment 1 pstodulk 2016-06-24 10:27:53 UTC
I close this old bug because nobody have time for fixing for many years and epel-5 is nearly in the end of life.


Note You need to log in before you can comment on or make changes to this bug.