unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: [GNU-Emacs] request: better subject lines
Date: Thu, 04 May 2017 04:01:38 +0200	[thread overview]
Message-ID: <87wp9xtm65.fsf@debian.uxu> (raw)
In-Reply-To: 20170502230426626149279@bob.proulx.com

Bob Proulx <bob@proulx.com> writes:

> For those wishing to read up on the saga these three
> in this order should get you up to speed on things.
>
>   https://lars.ingebrigtsen.no/2016/07/28/the-end-of-gmane/

I read that article back then, and I remember on one
of the groups (be it gmane.discuss) everyone,
including YT, encouraged Lars not to quit or to have
it handed over to someone else. What I remember he all
but instantly agreed not to have Gmane
disappear completely.

How anyone can have an IT job, Gnus, Gmane,
what's-the-name-of-the-web-browser (including
documentation) *and* a blog is beyond me. I don't
know, man.

Anyway if you read that article, you *do* get the
impression that it is the archive and web interface
that is the key part of Gmane. So maybe people
actually used that!

Except for this paragraph that sums it all up:

    The nice thing about a mailing list archive (with
    NNTP and HTTP interfaces) is that it enables
    software maintainers to say (whenever somebody
    suggests using Spiffy Collaboration Tool of the
    Month instead of yucky mailing lists) is “well,
    just read the stuff on Gmane, then”. I feel like
    I’m letting down a generation here.

Ha ha, I likewise very much dislike the "SCTs"!

-- 
underground experts united .... http://user.it.uu.se/~embe8573
Emacs Gnus Blogomatic ......... http://user.it.uu.se/~embe8573/blogomatic
                   - so far: 26 Blogomatic articles -                   




  parent reply	other threads:[~2017-05-04  2:01 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-30 15:39 [GNU-Emacs] request: better subject lines Carlos Konstanski
2017-04-30 16:38 ` Óscar Fuentes
2017-04-30 17:15 ` allan gottlieb
2017-05-01  3:03 ` Emanuel Berg
2017-05-02 12:52 ` [Emacs] " ken
2017-05-02 13:41   ` tomas
2017-05-02 15:12     ` Danny YUE
2017-05-03  8:49       ` tomas
2017-05-03  9:49         ` Danny YUE
2017-05-03 10:26           ` tomas
2017-05-02 17:05     ` ken
2017-05-02 17:32       ` hector
2017-05-02 18:38       ` Bob Proulx
2017-05-03  8:56         ` tomas
2017-05-02 14:34   ` Harry Putnam
2017-05-02 19:04     ` Emanuel Berg
2017-05-02 20:43 ` [GNU-Emacs] " Bob Proulx
2017-05-03  0:57   ` Emanuel Berg
2017-05-03  5:10     ` Bob Proulx
2017-05-03 12:38       ` Óscar Fuentes
2017-05-03 20:12       ` Emanuel Berg
2017-05-03 23:25         ` Nick Dokos
2017-05-04  1:34           ` Emanuel Berg
2017-05-04 17:02             ` Nick Dokos
2017-05-04 18:29               ` Emanuel Berg
2017-05-04  5:26         ` Marcin Borkowski
2017-05-04  6:55           ` Emanuel Berg
2017-05-04  6:59           ` Emanuel Berg
2017-05-04  2:01       ` Emanuel Berg [this message]
2017-05-03  2:34   ` allan gottlieb
2017-05-04 15:40     ` Emanuel Berg

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wp9xtm65.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).