Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
To: info-gnus-english@gnu.org
Subject: Re: Change in splitting from emacs 22/gnus 5.11 and emacs 23/gnus 5.13?
Date: Wed, 13 Jan 2010 23:05:39 +0100	[thread overview]
Message-ID: <877hrlirt8.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87d41dvftv.fsf@lifelogs.com>

On Wed, 13 Jan 2010 15:46:04 -0600, Ted wrote:

> We should think about a gnus-snarf-configuration that will report this
> kind of detail. It's hard for the users to give us exactly what we
> need to find Gnus configuration issues, because Gnus configuration is
> spread over such a wide namespace.

Yeah.

Although, he did say, quite early on:

On Thu, 07 Jan 2010 10:10:50 -0800, Kendall Shaw wrote:

> and mail-sources is nil

... which wasn't quite true, so... It's not like it wasn't one of the
things we asked about pretty early on.

(Although I only now realize that he changed names for that one reply -
otherwise his name was Frank Fredstone...)


  Best regards,

    Adam

-- 
 "The concert is finito, my friends, goodnight!"              Adam Sjøgren
                                                         asjo@koldfront.dk

  reply	other threads:[~2010-01-13 22:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-04 21:56 Frank Fredstone
2010-01-05 18:53 ` Ted Zlatanov
2010-01-05 19:37   ` Frank Fredstone
2010-01-05 20:38     ` Ted Zlatanov
2010-01-05 20:52       ` Frank Fredstone
2010-01-06 15:24         ` Ted Zlatanov
2010-01-07  0:50           ` Frank Fredstone
2010-01-07 14:21             ` Adam Sjøgren
2010-01-07 18:10               ` Kendall Shaw
2010-01-07 18:33                 ` Adam Sjøgren
2010-01-07 18:52                   ` Frank Fredstone
2010-01-07 18:53                     ` Adam Sjøgren
2010-01-07 19:13                       ` Frank Fredstone
2010-01-07 19:52                         ` Adam Sjøgren
2010-01-07 20:16                           ` Frank Fredstone
2010-01-07 20:27                             ` Adam Sjøgren
2010-01-08 15:52                 ` Ted Zlatanov
2010-01-08 18:57                   ` Frank Fredstone
2010-01-08 21:52                     ` Adam Sjøgren
2010-01-08 22:22                       ` Frank Fredstone
2010-01-08 22:31                         ` Adam Sjøgren
2010-01-09  0:33                           ` Frank Fredstone
2010-01-09  2:06                             ` Adam Sjøgren
2010-01-13 21:46                           ` Ted Zlatanov
2010-01-13 22:05                             ` Adam Sjøgren [this message]
2010-01-14 14:21                               ` better bug reporting (was: Change in splitting from emacs 22/gnus 5.11 and emacs 23/gnus 5.13?) Ted Zlatanov
2010-01-14 14:33                                 ` better bug reporting Adam Sjøgren
2010-01-08 22:17                     ` Change in splitting from emacs 22/gnus 5.11 and emacs 23/gnus 5.13? Ted Zlatanov
2010-01-08 22:39                       ` Frank Fredstone
2010-01-07 15:33             ` Ted Zlatanov

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=877hrlirt8.fsf@topper.koldfront.dk \
    --to=asjo@koldfront.dk \
    --cc=info-gnus-english@gnu.org \
    /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).