Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ContributorsFromGit] -> [Git::Contributors] #73

Closed
wants to merge 1 commit into from

Conversation

karenetheridge
Copy link

This plugin has unresolved issues on MSWin32 and with handling unicode names, so I forked it last year.

This plugin has unresolved issues on MSWin32 and with handling unicode names, so I forked it last year.
@tsibley
Copy link
Collaborator

tsibley commented Jan 23, 2016

Thanks for the heads up @ether. None of the releasers of recs are using Windows, so that shouldn't be a big deal, I think. What are the Unicode fixes? I'd like to understand what's changed before I switch it up. It'd be nice if Git::Contributors had a "differences from ContributorsFromGit" section in the doc. :-)

@karenetheridge
Copy link
Author

The differences from the other plugin would be a rather large list. Aside from the options to allow different sorting orders and whether to include authors and/or releasers, bug fixes include proper decoding of the author's and releaser's name (so on ContributorsFromGit, if your name is Olivier Mengué, you're just SOL), and not messing around with the user's podweaver configuration. Also there is a workaround for unicode issues on older JSON::PP on older perls (where any JSON::PP before the latest release would cause an install to blow up if META.json contained any unicode data, anywhere, meaning a distribution with a non-ascii contributor name would be uninstallable on perl 5.6).

tsibley added a commit that referenced this pull request Feb 26, 2016
ETHER makes the case for this on GH #73.  She's kinda the queen of dzil,
so I trust her judgment.  :)
@tsibley
Copy link
Collaborator

tsibley commented Feb 26, 2016

Closed with 2772c47. I actually forgot that this was a PR and not an issue, so I made the change myself in a new commit.

@tsibley tsibley closed this Feb 26, 2016
@karenetheridge
Copy link
Author

no worries, cheers!

@karenetheridge karenetheridge deleted the patch-1 branch February 26, 2016 05:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants