Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: tricky explicit interactive verbosity
Date: Tue, 14 Nov 2017 13:53:28 -0800	[thread overview]
Message-ID: <87inecsf1j.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <86h8tw1uqv.fsf@zoho.com>

Emanuel Berg <moasen@zoho.com> writes:

> Eric Abrahamsen wrote:
>
>> It doesn't look like
>> `gnus-summary-current-score' is used
>> programmatically at all, so I'm not sure why
>> it would need to use gnus-message in the
>> first place. Other code can (and does) use
>> whichever of `gnus-summary-article-score' or
>> `gnus-thread-total-score' is necessary.
>>
>> I'd be in favor of just using `message'.
>
> This brings to mind something I've thought
> about, namely how does Gnus development work?
> Should one submit patches thru some formal
> procedure with the hope it gets accepted, or
> report it as a bug, or just mention it here?
> This particular issue could be a good exercise
> because it is so trivial and harmless to begin
> with :)

I'd say raise questions here, and if you don't get a satisfactory
answer, use `gnus-bug'.

Gnus development is a bit of a conundrum at the moment. Katsumi Yamaoka
seems to have the MIME stuff well in hand, but the rest of it is kind of
a free-for-all. I'm nudging myself in to the group/server area, and also
into picking off low-hanging fruit (eg your report). I intend to keep
doing this until I boff something up royally, and/or someone tells me to
cut it out.

So when I say "I'd be in favor of...", that actually means "I will push
this change to master in three or four days, unless someone says not
to".

Eric




  reply	other threads:[~2017-11-14 21:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-12 17:42 Emanuel Berg
2017-11-14 16:22 ` Eric Abrahamsen
2017-11-14 20:16   ` Emanuel Berg
2017-11-14 21:53     ` Eric Abrahamsen [this message]
2017-11-20 22:23       ` Eric Abrahamsen

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=87inecsf1j.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.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).