Re: [savannah-help-public] Wrong encoding in commit messages sent to groff-commit

Werner LEMBERG wrote: > > I don't know. Both Mailman and the list archives are managed by the > > FSF admins. AFAIK the Savannah Hackers have no access to them. It > > does appear broken on the index page. > > Can you ping them? This is general problem of *all* gnu.org and > nongnu.org mailing

Re: [savannah-help-public] Wrong encoding in commit messages sent to groff-commit

>> UTF-8 encoding for the `threads.html' pages, possibly converting >> non-UTF-8 encodings in e-mail headers to UTF-8. Maybe this has >> been fixed meanwhile? Or maybe it's a configuration thing that >> gnu.org hasn't adjusted properly? > > I don't know. Both Mailman and the list archives are

Re: [savannah-help-public] Wrong encoding in commit messages sent to groff-commit

Werner LEMBERG wrote: > > http://lists.gnu.org/archive/html/emacs-elpa-diffs/2014-01/threads.html > > Uh, oh, on this page I immediately see mojibake: > > [ELPA-diffs] [elpa] 01/01: Start building eventu al package \ > ‘gnugo’., Thien-Thi Nguyen, 2014/01/28 Yuck. > This is a problem

Re: [savannah-help-public] Wrong encoding in commit messages sent to groff-commit

> The emacs elpa folks just requested to change their hook to the > git-multimail mailer hook. Very nice! > I just installed it for them just a few days ago. Look at their new > commit diffs. > > http://lists.gnu.org/archive/html/emacs-elpa-diffs/2014-01/threads.html Uh, oh, on this page I i

[savannah-help-public] [sr #108467] Please change GNU ELPA post receive hook to new multimail email hook

Follow-up Comment #10, sr #108467 (project administration): Nope. You were right. It did need to be in the hooks directory. The cwd is definitely above it however. I tested this by synthesizing a commit. I think it should be good to go. ___

[savannah-help-public] [sr #108467] Please change GNU ELPA post receive hook to new multimail email hook

Follow-up Comment #9, sr #108467 (project administration): I think the hook script is called with a cwd of elpa.git and called like echo $oldrev $newrev $refname | ./hooks/post-receive and therefore the import needs to be relative to the elpa.git directory and not the hooks directory. I could be

[savannah-help-public] [sr #108467] Please change GNU ELPA post receive hook to new multimail email hook

Follow-up Comment #8, sr #108467 (project administration): Thanks. But looking at http://git.savannah.gnu.org/r/emacs/elpa.git/ I think you put git_multimail.py in the wrong directory. Shouldn't it be in http://git.savannah.gnu.org/r/emacs/elpa.git/hooks/ instead of elpa.git/? _

[savannah-help-public] [sr #108467] Please change GNU ELPA post receive hook to new multimail email hook

Follow-up Comment #7, sr #108467 (project administration): I modified the post-receive hook as per this message: http://lists.gnu.org/archive/html/emacs-devel/2014-01/msg01954.html ___ Reply to this item at:

Re: [savannah-help-public] Wrong encoding in commit messages sent to groff-commit

Werner LEMBERG wrote: > > Author: Ulrich Sp??rlein > > +2014-01-28 Ulrich Sp??rlein > > Have a look at the attched commit message e-mail. It contains some > mojibake, namely UTF-8 characters represented as Latin-1. > > Any chance that this gets fixed? I can imagine that today it's a > rathe

[savannah-help-public] Wrong encoding in commit messages sent to groff-commit

Have a look at the attched commit message e-mail. It contains some mojibake, namely UTF-8 characters represented as Latin-1. Any chance that this gets fixed? I can imagine that today it's a rather safe bet to assume UTF-8 encoding for commit messages... Or maybe this could be adjusted in the p