From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Separate Outbox and Draft
Date: Thu, 22 Jun 2023 17:10:58 +0200 [thread overview]
Message-ID: <20230622151058.PnCR8AJXyLc-LKWV2flAOnh_u2NuBFr9WFKR_xUVrKI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-240@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 186 bytes --]
New comment by leahneukirchen on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/240#issuecomment-1602814830
Comment:
It's a reasonable feature, yes. Wanna try a PR?
next prev parent reply other threads:[~2023-06-22 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 15:50 [ISSUE] " thyssentishman
2023-06-22 15:10 ` leahneukirchen [this message]
2023-06-22 17:38 ` thyssentishman
2023-06-22 20:15 ` [ISSUE] [CLOSED] " leahneukirchen
2023-06-22 20:39 ` thyssentishman
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=20230622151058.PnCR8AJXyLc-LKWV2flAOnh_u2NuBFr9WFKR_xUVrKI@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).