From: Kyle Meyer <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>
Subject: Re: Bug: org-clone-subtree-with-time-shift throws error [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]
Date: Mon, 23 Nov 2020 17:58:18 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
> Thanks for the reply. I used the version shipped with emacs in the
> report, and now I installed org 9.4 from the gnu default repository
> via package-list-packages within emacs and the error indeed goes
> away. Is that the recommended stable version to use?
I suppose it depends largely on the user. For many, the version of Org
bundled with Emacs will do, and it's not worth the hassle of installing
it from another source. But, if you've hit into a bug that's fixed in
the latest release or just always want to keep up with the latest
release, then the default ELPA source is a good choice.
There's also Org's ELPA archives, if you instead wanted code based off
of the maint branch.
> Should I report bugs against the latest git version only?
Reporting a bug against the Org bundled with Emacs is fine. Many times
this issue is still around, and a fix is applied to the maint branch and
will be included in the next release. But if it turns out that it's
already fixed, then there's no other action we take on our end.
However, if a reporter is willing to take the time to check the latest
release (or even the maint or master branch) or search the mailing list
archives, that's of course appreciated and helpful.
next prev parent reply other threads:[~2020-11-23 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 8:59 Bug: org-clone-subtree-with-time-shift throws error [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)] skaphle
2020-11-20 6:06 ` Kyle Meyer
2020-11-23 12:54 ` skaphle
2020-11-23 22:58 ` Kyle Meyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-15 16:00 skaphle
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).