Reviewing merge request #2: Fix adding encoded email address

The commit message is explicit by itself :)

Previously, From line of the form "=?iso-8859-1?q?p=F6stal?= <foo@bar>"
would be submitted as it. Now, the name is correctly decoded according
to the encoding specified in the value.

This is defined by the RFC 2047, you can find more information at
http://docs.python.org/library/email.header.html

Requested by: Jonathan Ballet
Status: Closed
Source repository: fix-encoding:master
Target repository: mainline:master
Created at: January 28th, 2012 11:32

Commits that would be merged:

Version 1

Version 1

6690c53
81a8516

Correctly decode encoded From headers

Showing

Showing 6690c53-81a8516

Comments
Include comments entered inline

Pushed new version 1

Jonathan Ballet | 2012-01-28 11:32:43 UTC

Hi, and thanks, I will look at this i a few days.

Christer Sjöholm | 2012-02-01 12:48:34 UTC

→ State changed from Open to Closed

It’s now merged inte master

Christer Sjöholm | 2012-02-17 13:24:59 UTC

Add a new comment:

Login or create an account to post a comment

How to apply this merge request to your repository

One way to merge in these changes is to pull them into a local branch for review, verifying the changes and then merge to back to master.

# Check out a new branch for integration
git checkout -b merge-requests/2

# Fetch the merge request into this branch
git pull \
  git://gitorious.org/goobook/mainline.git \
  refs/merge-requests/2

# Show the commits, assess they are okay
git log --pretty=oneline --abbrev-commit master..merge-requests/2

# To apply the changes to your branch:
git checkout master
git merge merge-requests/2
git push origin master

Reviewing merge request #2: Fix adding encoded email address

Commits that would be merged:

Comments Include comments entered inline

Add a new comment:

Gitorious

Comments
Include comments entered inline