From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: New branch: girzel/gnus-headers
Date: Sun, 03 Jan 2021 11:37:11 +0100 [thread overview]
Message-ID: <87v9ce8fxk.fsf@gnus.org> (raw)
In-Reply-To: <m21rf2l39j.fsf@codeisgreat.org> (Pankaj Jangid's message of "Sun, 03 Jan 2021 16:02:24 +0530")
Pankaj Jangid <pankaj@codeisgreat.org> writes:
> But I would like to try this feature again. Let me try it for gwene
> groups. Are the docs also updated in the above mentioned branch?
Yes.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-01-03 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 7:50 Lars Ingebrigtsen
2021-01-03 10:32 ` Pankaj Jangid
2021-01-03 10:37 ` Lars Ingebrigtsen [this message]
2021-01-04 21:23 ` 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=87v9ce8fxk.fsf@gnus.org \
--to=larsi@gnus.org \
--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).