From: delyan@sonic.net
To: autofs@vger.kernel.org, backports+subscribe@vger.kernel.org,
backports+unsubscribe@vger.kernel.org, backports@vger.kernel.org,
bpf+subscribe@vger.kernel.org, bpf+unsubscribe@vger.kernel.org,
bpf@vger.kernel.org, ceph-devel+subscribe@vger.kernel.org,
ceph-devel+unsubscribe@vger.kernel.org,
ceph-devel@vger.kernel.org, cgroups+subscribe@vger.kernel.org,
cgroups+unsubscribe@vger.kernel.org, cgroups@vger.kernel.org,
dash+subscribe@vger.kernel.org, dash+unsubscribe@vger.kernel.org,
dash@vger.kernel.org, dccp+subscribe@vger.kernel.org,
dccp+unsubscribe@vger.kernel.org, dccp@vger.kernel.org,
devicetree+subscribe@vger.kernel.org,
devicetree+unsubscribe@vger.kernel.org,
devicetree@vger.kernel.org,
devicetree-compiler+subscribe@vger.kernel.org,
devicetree-compiler+unsubscribe@vger.kernel.org,
devicetree-compiler@vger.kernel.org,
devicetree-spec+subscribe@vger.kernel.org
Subject: subscribe
Date: Tue, 27 Feb 2024 01:52:18 -0500 [thread overview]
Message-ID: <65DD86A2.27104.445FAB06@delyan.sonic.net> (raw)
subscribe
reply other threads:[~2024-02-27 6:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=65DD86A2.27104.445FAB06@delyan.sonic.net \
--to=delyan@sonic.net \
--cc=autofs@vger.kernel.org \
--cc=backports+subscribe@vger.kernel.org \
--cc=backports+unsubscribe@vger.kernel.org \
--cc=backports@vger.kernel.org \
--cc=bpf+subscribe@vger.kernel.org \
--cc=bpf+unsubscribe@vger.kernel.org \
--cc=bpf@vger.kernel.org \
--cc=ceph-devel+subscribe@vger.kernel.org \
--cc=ceph-devel+unsubscribe@vger.kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=cgroups+subscribe@vger.kernel.org \
--cc=cgroups+unsubscribe@vger.kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=dash+subscribe@vger.kernel.org \
--cc=dash+unsubscribe@vger.kernel.org \
--cc=dash@vger.kernel.org \
--cc=dccp+subscribe@vger.kernel.org \
--cc=dccp+unsubscribe@vger.kernel.org \
--cc=dccp@vger.kernel.org \
--cc=devicetree+subscribe@vger.kernel.org \
--cc=devicetree+unsubscribe@vger.kernel.org \
--cc=devicetree-compiler+subscribe@vger.kernel.org \
--cc=devicetree-compiler+unsubscribe@vger.kernel.org \
--cc=devicetree-compiler@vger.kernel.org \
--cc=devicetree-spec+subscribe@vger.kernel.org \
--cc=devicetree@vger.kernel.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).