From: TEC <email@example.com>
Subject: Re: [Interest] Determanistic Org IDs
Date: Mon, 20 Jul 2020 11:45:35 +0800 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Noticed some autoformatting happened on send. This is how the cons
paragraph /should/ read (with a minor correction as well).
*In last email*
> Cons: - Inceased chance of ID collisions across files Longer IDs
> I - think this could make a nice option for export settings.
> I'm - aware of the 9.5 feature freeze, but thought I'd mention
> the - idea to see if there's any interest in it.
- Inceased chance of ID collisions across files
- Longer IDs
I think this could make a nice option for export settings. I'm
aware of the 9.4 feature freeze, but thought I'd mention the idea
to see if there's any interest in it.
Hope that makes things clearer.
Please do let me know what you think, this would be my second
contribution, so I still very much feel like I'm finding my feet.
All the best,
next parent reply other threads:[~2020-07-20 3:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1jxAkG-00052l-OS@lists.gnu.org>
2020-07-20 3:45 ` TEC [this message]
[not found] <E1jxAju-0004Dk-3O@lists.gnu.org>
2020-07-24 12:09 ` [Interest] Determanistic Org IDs Alexander Adolf
2020-07-24 14:53 ` TEC
2020-07-19 14:27 TEC
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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).