From: Julien Danjou <julien@danjou.info>
To: John Sullivan <john@wjsullivan.net>
Cc: ding@gnus.org
Subject: Re: Gcc not being respected in nnimap group
Date: Wed, 17 Nov 2010 10:47:41 +0100 [thread overview]
Message-ID: <sa3k4kcuvr6.fsf@cigue.easter-eggs.fr> (raw)
In-Reply-To: <sa3r5ekuw97.fsf@cigue.easter-eggs.fr> (Julien Danjou's message of "Wed, 17 Nov 2010 10:36:52 +0100")
On Wed, Nov 17 2010, Julien Danjou wrote:
> I noticed it yesterday too. I did not find the commit culprit yet…
Actually, I don't know if it's a regression or my configuration which
was broken, but the group name for the primary method is not fully
qualified with its method.
--
Julien Danjou
// ᐰ <julien@danjou.info> http://julien.danjou.info
next prev parent reply other threads:[~2010-11-17 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 21:17 John Sullivan
2010-11-17 9:36 ` Julien Danjou
2010-11-17 9:47 ` Julien Danjou [this message]
2010-11-17 16:22 ` John Sullivan
2010-11-17 18:06 ` Julien Danjou
2010-11-17 18:54 ` John Sullivan
2010-11-17 19:22 ` Julien Danjou
2010-11-19 21:20 ` John Sullivan
2010-11-20 11:23 ` Julien Danjou
2010-11-20 22:42 ` John Sullivan
2010-11-21 13:29 ` Julien Danjou
2010-11-24 18:21 ` John Sullivan
2010-11-24 19:23 ` Julien Danjou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=sa3k4kcuvr6.fsf@cigue.easter-eggs.fr \
--to=julien@danjou.info \
--cc=ding@gnus.org \
--cc=john@wjsullivan.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).