Werner LEMBERG wrote:
> > I can unsubscribe your second address.
>
> Please do that!
Done!
> Thanks for checking and all your help!
Happy to help.
Bob
> You are subscribed *twice* to the groff-commit mailing list! :-)
Doh. This never occurred to me.
> You have both your normal address there and an additional wl AT
> vcs.savannah.gnu.org address also subscribed there. Check out the
> groff-commit subscriber list. That is definitely the secon
Werner LEMBERG wrote:
>
> > Could you forward two messages with all of the Received headers intact
> > so that we could trace through the mail relays and see where it came
> > through?
>
> Both are attached. Thanks for investigating this!
Sorry for the long delay. I finally got some time to lo
> Could you forward two messages with all of the Received headers intact
> so that we could trace through the mail relays and see where it came
> through?
Both are attached. Thanks for investigating this!
>> Additionally, the `Reply-To' field is set to the author of the
>> patch. However, I wo
Werner LEMBERG wrote:
> > In the meantime I will change the config to this one. I think that
> > will prevent the sending of the branch change notification but will
> > still preserve the individual commit notifications.
> >
> >mailinglist =
> >commitList = groff-com...@gnu.org
>
> This w
> In the meantime I will change the config to this one. I think that
> will prevent the sending of the branch change notification but will
> still preserve the individual commit notifications.
>
>mailinglist =
>commitList = groff-com...@gnu.org
This works, thanks. However, there are som
Werner LEMBERG wrote:
> I've just committed a tiny change to groff, and now *two* e-mails are
> sent to the `groff-commit' list. This is overkill IMHO.
There is one message to notify of the change to the branch status.
Then there is one email for each individual commit. If you were
pushing twent
>> > What Mail-Follow-Up address would you like? bug-groff or groff or
>> > back to groff-commit?
>>
>> Please use `groff' as the Mail-Follow-Up address.
>
> Done. Let us know what you think.
I've just committed a tiny change to groff, and now *two* e-mails are
sent to the `groff-commit' list
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
>> 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
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
> 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
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
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
14 matches
Mail list logo
