Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Calling for testers: scratch/gnus-decoded branch
Date: Thu, 06 Jun 2019 20:58:11 -0700	[thread overview]
Message-ID: <87wohydp2k.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <86lfyenklp.fsf@zoho.eu>

Emanuel Berg <moasenwood@zoho.eu> writes:

> Eric Abrahamsen wrote:
>
>>> Or ask professional computer people, in the
>>> IT-industry! As they work 70+ hours a week
>>> they seem to have even more time...
>>
>> Hey Emanuel! You don't seem busy, do you
>> build Emacs from git? Want to help me test
>> the scratch/gnus-decoded branch?
>
> First, I'm busy. I run a bike repair shop.
> It is on a DIY basis, but someone has to
> maintain order and see to it every day that its
> clean and tools aren't abused and end up it
> their right places, clean and operational and
> ready to use for the next guy. Here is a couple
> of photos [1]. I don't sleep many hours
> a night, believe me.

I know, I was just being a jerk ;)

> Second, while I'd love to help, I don't know
> how to do it in that form. My Gnus is so
> super-configured and -extended it would be near
> impossible to track what and where an error
> would be, if I found one. I don't even know how
> to use Gnus without all that extra stuff of
> mine. I'd be completely lost.

It's the easiest kind of help I'm asking for -- just turn it on and see
if it explodes! The branch in question has to do with the encoding and
coding of group names. If you have groups with non-ascii names in
particular (accents, etc), it would be helpful just to know if they
display correctly, if you can jump to it, move articles into and out of
them, etc.

I've just pushed another commit to the branch which means you don't have
to backup your .newsrc.eld before testing the branch. I mean, you still
ought to, but the code shouldn't mess with the format of the file.

Anyway, no one has any obligation to spend time on this! It was mean of
me to single you out, it was only because you showed up in the thread :)

Eric




  reply	other threads:[~2019-06-07  3:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  0:59 Eric Abrahamsen
2019-06-04  5:24 ` Eric Abrahamsen
2019-06-06  2:38   ` Michael Heerdegen
2019-06-06  2:48     ` Emanuel Berg
2019-06-06 23:07       ` Eric Abrahamsen
2019-06-07  3:24         ` Emanuel Berg
2019-06-07  3:58           ` Eric Abrahamsen [this message]
2019-06-07  4:15             ` Emanuel Berg
2019-06-07  5:44               ` Eric Abrahamsen
2019-06-07 15:22                 ` Emanuel Berg
2019-06-07 16:52                   ` Eric Abrahamsen
2019-06-08 21:01                     ` Emanuel Berg
2019-06-06  9:14 ` Andy Moreton
2019-06-06 23:47   ` Eric Abrahamsen
2019-06-07  9:48     ` Tassilo Horn
2019-06-07 16:46       ` Eric Abrahamsen
2019-06-07 22:41 ` Adam Sjøgren
2019-06-10  4:18   ` Eric Abrahamsen
2019-06-16 13:24     ` Adam Sjøgren
2019-06-16 16:53       ` Eric Abrahamsen
2019-06-16 19:06         ` Adam Sjøgren
2019-06-16 19:45           ` Eric Abrahamsen
2019-06-16 20:01             ` Adam Sjøgren
2019-06-16 20:57               ` Eric Abrahamsen
2019-06-16 21:25                 ` Eric Abrahamsen
2019-07-20  9:22                 ` Adam Sjøgren
2019-07-21  3:19                   ` Eric Abrahamsen
2019-07-21 10:08                     ` Adam Sjøgren
2019-07-22 17:05                       ` Eric Abrahamsen
2019-07-22 17:08                         ` Adam Sjøgren
2019-06-16 19:45           ` 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=87wohydp2k.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).