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

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

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

Aliases:	None

Product:	Fedora EPEL
Classification:	Fedora
Component:	git (Show other bugs)
Sub Component:
Version:	el5
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Chris Wright
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-06-29 07:34 EDT by Kirby Zhou
Modified:	2016-06-24 06:27 EDT (History)
CC List:	8 users (show)

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

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Kirby Zhou 2010-06-29 07:34:29 EDT

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 06:27:53 EDT

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.