Unnamed repository; edit this file 'description' to name the repository.
 help / color / mirror / Atom feed
From: Rafi Khan <rafi@rafikhan.io>
To: "Adam Sjøgren via info-gnus-english" <info-gnus-english@gnu.org>
Cc: "Adam Sjøgren" <asjo@koldfront.dk>
Subject: Re: Test email
Date: Fri, 10 Jul 2020 19:47:56 -0400
Message-ID: <87eepjue37.fsf@rafikhan.io> (raw)
In-Reply-To: <875zaverel.fsf@tullinup.koldfront.dk> ("Adam =?utf-8?Q?Sj?= =?utf-8?Q?=C3=B8gren?= via info-gnus-english"'s message of "Fri, 10 Jul 2020 09:54:42 +0200")

Adam Sjøgren via info-gnus-english <info-gnus-english@gnu.org> writes:

Adam Sjøgren via info-gnus-english <info-gnus-english@gnu.org> writes:

> The first strategy is useful if the person writing on the mailing list
> isn't subscribed to it. (I find that an odd thing to do, and with Gmane,
> where following a mailing list is very low friction, even more so).

I see, thank you for the explanation! I'm starting to understand now.


info-gnus-english mailing list

  reply	other threads:[~2020-07-11  0:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09  5:15 Rafi Khan
2020-07-09  7:31 ` Alberto Luaces
2020-07-10  0:14   ` Rafi Khan
2020-07-10  7:54     ` Adam Sjøgren via info-gnus-english
2020-07-10 23:47       ` Rafi Khan [this message]
2020-07-10 13:18     ` ‘Reply’ vs ‘followup’ (was: Test email) Dmitry Alexandrov
2020-07-10 14:14       ` ‘Reply’ vs ‘followup’ Alberto Luaces
2020-07-10 15:28       ` Adam Sjøgren via info-gnus-english
2020-07-10 23:51       ` Rafi Khan
2020-07-09  8:17 ` Test email Dmitry Alexandrov
     [not found]   ` <87imewz0ui.fsf@rafikhan.io>
2020-07-10  4:26     ` Get list address for Gmane group (was: Test email) Dmitry Alexandrov
2020-08-06 12:53 ` Test email 황병희
2020-08-07  4:01   ` Rafi Khan
2020-08-08  2:31     ` 황병희
2020-08-08 15:39       ` Emanuel Berg via info-gnus-english

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:

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

  git send-email \
    --in-reply-to=87eepjue37.fsf@rafikhan.io \
    --to=rafi@rafikhan.io \
    --cc=asjo@koldfront.dk \
    --cc=info-gnus-english@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Unnamed repository; edit this file 'description' to name the repository.

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.vuxu.org/info-gnus-english

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 info-gnus-english info-gnus-english/ http://inbox.vuxu.org/info-gnus-english \
	public-inbox-index info-gnus-english

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git