From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: create a message, have it in the holster?
Date: Tue, 26 Sep 2017 09:53:36 -0700 [thread overview]
Message-ID: <87o9pxpfjj.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87bmlx1pcn.fsf@local.lan>
Harry Putnam <reader@newsguy.com> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
> [...]
>
> Emanual B wrote:
>>> PS. Is this a question for
>>> gmane.emacs.gnus.general or
>>> gmane.emacs.gnus.user ?
>>
>
> Eric A wrote
>> PS I don't know that there's any difference between the two lists at
>> this point, and kind of think it would be better for
>> gmane.emacs.gnus.user to go away.
>
> Repectfully wish to disagree with this.
>
> I (for one) continue to use gmane.emacs.gnus.user in this way:
> I sometimes have questions about common functioning of gnus, perhaps
> things I once knew but forgot and having a time finding in manual.
> (and that might be pretty common amongst the 70+ yrs gang I belong to)
Well, sure -- I guess I wasn't really proposing that we delete the
group, it just seems like both lists are low-traffic enough that we
wouldn't really need two.
> Or just things I never had occasion to use until now, but that I know
> are long time abilities.
>
> I suppose it could be argued that those very things may well have
> changed in more recent versions and therefore more appropriate to
> gmane.emacs.gnus.general but as a long time user I think I have some
> fairly good notions about what is old stuff or not.
>
> I suspect there are more than a few others who feel they know the
> difference and know when to post to which group. In fact I would have
> guessed that Emanual B, would have been one of those.
>
> Plus there is always the process of posting to ...user and if no
> answer comes in a few days, move it to ...general.
I guess it would be less confusing if they were called "user" and
"devel". Anyway, it's certainly no big deal to have two.
> I suppose this is quite subjective, but still, I suspect what I say
> above is pretty close to true.
>
> One other point is that it would be a waste of talent to tie up people
> like Eric A with mundane questions that can be answered by other old
> hands.
That's kind of you, but I don't know how to answer half of the questions
that get posted here!
Eric
next prev parent reply other threads:[~2017-09-26 16:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 8:31 Emanuel Berg
2017-09-25 15:28 ` Eric Abrahamsen
2017-09-25 18:46 ` Emanuel Berg
2017-09-25 19:32 ` Eric Abrahamsen
2017-09-25 21:39 ` Emanuel Berg
2017-10-01 4:42 ` Emanuel Berg
2017-10-01 13:07 ` Emanuel Berg
2017-09-25 15:38 ` Eric Abrahamsen
2017-09-25 18:46 ` Emanuel Berg
2017-09-26 14:55 ` Harry Putnam
2017-09-26 16:53 ` Eric Abrahamsen [this message]
2017-09-26 17:19 ` Adam Sjøgren
2017-09-26 19:46 ` 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=87o9pxpfjj.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).