From: Carsten Dominik <dominik@uva.nl>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: org-mode list <emacs-orgmode@gnu.org>
Subject: Re: Subject: Use of date trees in Capture has been modified
Date: Thu, 16 Mar 2017 12:41:59 +0100 [thread overview]
Message-ID: <CADn3Z2K4mMnadbsCBM0JLy14t47hhw_4uyAHSEsiAMfbBjokNg@mail.gmail.com> (raw)
In-Reply-To: <m28to5zkk3.fsf@polytechnique.org>
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
Hi Alan,
the change is not formally a breaking change, because everything will
continue to work as before.
But yes, such changes are usually documented.
Carsten
On Thu, Mar 16, 2017 at 9:34 AM, Alan Schmitt <
alan.schmitt@polytechnique.org> wrote:
> Hello Carsten,
>
> On 2017-03-16 08:55, Carsten Dominik <dominik@uva.nl> writes:
>
> > I have just pushed (to master) a patch that modifies the use
> > of date trees in capture templates. If you don't use them,
> > no need to read on.
>
> I can't update till this reaches maint (which I use), but I'll probably
> forget by then. I assume this change will be in NEWS, but is there a
> place where breaking changes are summarized for each release ?
>
> Thanks,
>
> Alan
>
> --
> OpenPGP Key ID : 040D0A3B4ED2E5C7
> Monthly Athmospheric CO₂, Mauna Loa Obs. 2017-02: 406.42, 2016-02: 404.04
>
[-- Attachment #2: Type: text/html, Size: 1427 bytes --]
next prev parent reply other threads:[~2017-03-16 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 7:55 Subject: Use of date trees in Capture has been modified Carsten Dominik
2017-03-16 8:34 ` Alan Schmitt
2017-03-16 11:41 ` Carsten Dominik [this message]
[not found] <59779b8073fa4f0683216c82e6ec9cce@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-16 9:39 ` Eric S Fraga
2017-03-16 10:10 ` Carsten Dominik
[not found] ` <b855abbe7ad14fcfbd3f76767d8a4a0b@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-16 19:12 ` Eric S Fraga
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADn3Z2K4mMnadbsCBM0JLy14t47hhw_4uyAHSEsiAMfbBjokNg@mail.gmail.com \
--to=dominik@uva.nl \
--cc=alan.schmitt@polytechnique.org \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).