From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: document depreciation of timeline?
Date: Mon, 24 Aug 2015 22:54:00 +0200 [thread overview]
Message-ID: <87d1yc9zmf.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20150824090725.GB13516@boo.workgroup> (Gregor Zattler's message of "Mon, 24 Aug 2015 11:07:25 +0200")
Hello,
Gregor Zattler <telegraph@gmx.net> writes:
> There are only two commits which mention the timeline in their
> summry lines in the newer git history since 2008-01-31.
>
> Shouldn't the feature then be officially depreciated and
> mentioned as stale in the manual? The manual mentions the
> timeline in most cases together with the agenda. And there is a
> small chapter dedicated to the timeline.
>
> If depreciation of the timeline is OK I would patch the manual
> accordingly.
I'm all for it. I think we shouldn't even document deprecated features
in the manual, otherwise, they just never go away.
In any case, Bastien will have the last word on the matter.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2015-08-24 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 4:00 Bug: Displaying timeline for .org-file and then switching to including inactive timestamps will not include old and future inactive timestamps [8.3.1 (8.3.1-16-gf6aa53-elpa @ /Users/cube/.emacs.d/elpa/org-20150810/)] Jakub Szypulka
2015-08-23 22:16 ` Nicolas Goaziou
2015-08-24 9:07 ` document depreciation of timeline? (was: Re: Bug: Displaying timeline for .org-file and then switching to including inactive timestamps will not include old and future inactive timestamps [8.3.1 (8.3.1-16-gf6aa53-elpa @ /Users/cube/.emacs.d/elpa/org-20150810/)]) Gregor Zattler
2015-08-24 20:54 ` Nicolas Goaziou [this message]
2015-08-24 12:50 ` Bug: Displaying timeline for .org-file and then switching to including inactive timestamps will not include old and future inactive timestamps [8.3.1 (8.3.1-16-gf6aa53-elpa @ /Users/cube/.emacs.d/elpa/org-20150810/)] Jakub Szypulka
2015-08-24 14:38 ` Nicolas Goaziou
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=87d1yc9zmf.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--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).