From: Kyle Meyer <kyle@kyleam.com>
To: Adam Porter <adam@alphapapa.net>, emacs-orgmode@gnu.org
Subject: Re: [PATCH] Add option to automatically align tags in agenda view
Date: Tue, 08 Aug 2017 14:19:07 -0400 [thread overview]
Message-ID: <8760dxudlw.fsf@kyleam.com> (raw)
In-Reply-To: <87wp6em4z0.fsf@alphapapa.net>
Adam Porter <adam@alphapapa.net> writes:
> Kyle Meyer <kyle@kyleam.com> writes:
[...]
>> Since you're changing the default value, shouldn't you add appropriate
>> values for the :version and :package-version keywords?
>
> Thanks, I didn't know about these. I set :package-version to 9.1, since
> that should be the next Org release, I guess.
Yep, master-only changes are using 9.1 for :package-version
$ git log -u -G":package-version" maint..master
> I set :version to 26.3 since I guess that will be the next Emacs
> release, although I don't know if it will include Org 9.1. Let me
> know if these need to be changed.
As you can see in the diffs above, master-only changes are using 26.1
for :version. Assuming Org 9.0.* ships with Emacs 26.1, these will be
wrong, but they can be updated all together once 26.2 is released.
>> It'd be good to mention this change in ORG-NEWS as well.
>
> I should have thought of that. Done.
Thanks. Did you forget to attach the patch?
> I don't know if this still technically qualifies as a tinychange. I've
> sent the email to request the CA form just in case.
I don't know either. How about I apply your *.el changes, and we can
update ORG-NEWS once your assignment comes through?
--
Kyle
next prev parent reply other threads:[~2017-08-08 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 13:56 [PATCH] Add option to automatically align tags in agenda view Adam Porter
2017-08-07 17:32 ` Kyle Meyer
2017-08-07 18:57 ` Adam Porter
2017-08-07 22:04 ` Kyle Meyer
2017-08-08 15:52 ` Adam Porter
2017-08-08 18:19 ` Kyle Meyer [this message]
2017-08-08 18:23 ` Kyle Meyer
2017-08-08 18:42 ` Adam Porter
2017-08-08 19:26 ` Kyle Meyer
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=8760dxudlw.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=adam@alphapapa.net \
--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).