From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Add Drafts profile key
Date: Thu, 22 Jun 2023 22:15:47 +0200 [thread overview]
Message-ID: <20230622201547.w71nzpGX51bDWJiTyTfDLoGITDdAj8Xt7GUW-VlRNxg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-241@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 288 bytes --]
There's a merged pull request on the mblaze repository
Add Drafts profile key
https://github.com/leahneukirchen/mblaze/pull/241
Description:
Allow the user to set a Drafts key in profile to store draft messages and sent messages separately if Outbox is set.
This commit closes #240
next prev parent reply other threads:[~2023-06-22 20:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 17:31 [PR PATCH] " thyssentishman
2023-06-22 17:46 ` leahneukirchen
2023-06-22 18:55 ` [PR PATCH] [Updated] " thyssentishman
2023-06-22 19:03 ` thyssentishman
2023-06-22 19:37 ` leahneukirchen
2023-06-22 19:38 ` leahneukirchen
2023-06-22 20:15 ` leahneukirchen [this message]
2023-06-23 6:56 ` thyssentishman
2023-06-23 6:58 ` thyssentishman
2023-06-23 8:00 ` thyssentishman
2023-06-23 8:00 ` 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=20230622201547.w71nzpGX51bDWJiTyTfDLoGITDdAj8Xt7GUW-VlRNxg@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).