From: Kyle Meyer <kyle@kyleam.com>
To: misc@inbox.kyleam.com
Subject: [org-link-edit] Version 1.2.0 released
Date: Sun, 19 Apr 2020 02:20:33 +0000 [thread overview]
Message-ID: <87a738rzbi.fsf@kyleam.com> (raw)
The latest release of Org Link Edit comes with only one functional
change: org-link-edit-transport-next-link will now ask the caller if an
existing description should be overwritten rather than unconditionally
aborting.
Internally updates were required for upstream changes in Org, and v9.3
is now the minimum requirement.
reply other threads:[~2020-04-19 2:20 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
List information: https://git.kyleam.com/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a738rzbi.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=misc@inbox.kyleam.com \
/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).