From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Ömer <oakasapoglu@gmail.com>
Cc: info-gnus-english@gnu.org
Subject: Re: test2
Date: Fri, 26 May 2023 05:10:41 +0300 [thread overview]
Message-ID: <878rdb971a.fsf@thaodan.de> (raw)
In-Reply-To: <m1pm6sz78y.fsf@192.168.1.86> (=?utf-8?Q?=22=C3=96mer=22's?= message of "Mon, 22 May 2023 19:00:13 +0300")
Ömer <oakasapoglu@gmail.com> writes:
> and the replies(r) are direct emails sent to the user
Try S-w or S-W.
See C-h f RET `gnus-summary-wide-reply`.
next prev parent reply other threads:[~2023-05-26 2:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 15:19 test2 Ömer
2023-05-22 15:45 ` test2 Ömer
2023-05-22 15:52 ` test2 Ömer
2023-05-22 16:00 ` test2 Ömer
2023-05-26 2:10 ` Björn Bidar [this message]
2023-05-22 16:08 ` test2 Ömer
2023-05-22 16:18 ` test2 Ömer
2023-05-26 2:20 ` test2 Byung-Hee HWANG
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=878rdb971a.fsf@thaodan.de \
--to=bjorn.bidar@thaodan.de \
--cc=info-gnus-english@gnu.org \
--cc=oakasapoglu@gmail.com \
/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).