all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Phillip Lord <phillip.lord@russet.org.uk>, emacs-devel@gnu.org
Subject: Re: Tests, Emacs-25 and Conditional Features
Date: Wed, 16 Mar 2016 17:48:53 +0200	[thread overview]
Message-ID: <2ec5e27e-8318-2e13-7d9b-25b9ea6c74a9@yandex.ru> (raw)
In-Reply-To: <87k2l2zgre.fsf@russet.org.uk>

On 03/16/2016 03:36 PM, Phillip Lord wrote:

> First, does the "no changes on Emacs-25" rule apply to changes in the
> test directory -- i.e. can next tests be added. Arguments for -- tests
> are a good thing to add and should not break a release. Arguments
> against -- we are in pre-test, and it's easier to have a simple rule.
> Also, tests are currently painful to merge.

I think it's fine (I'm guilty of this myself), but you should be 
prepared to help merging, or to at least verify the result of the merge 
to master.



  parent reply	other threads:[~2016-03-16 15:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 13:36 Tests, Emacs-25 and Conditional Features Phillip Lord
2016-03-16 14:29 ` Michael Albinus
2016-03-17 10:14   ` Phillip Lord
2016-03-17 16:25     ` Eli Zaretskii
2016-03-18 10:41       ` Phillip Lord
2016-03-18 11:00         ` Michael Albinus
2016-03-18 17:19           ` Phillip Lord
2016-03-18 18:38             ` Eli Zaretskii
2016-03-18 11:07         ` Eli Zaretskii
2016-03-18 17:20           ` Phillip Lord
2016-03-18 18:37             ` Eli Zaretskii
2016-03-19 21:26               ` Phillip Lord
2016-03-18 15:15     ` Stefan Monnier
2016-03-18 15:41       ` Eli Zaretskii
2016-03-18 15:54         ` Stefan Monnier
2016-03-18 18:32           ` Eli Zaretskii
2016-03-18 17:22         ` Phillip Lord
2016-03-16 15:48 ` Dmitry Gutov [this message]
2016-03-16 16:12 ` Eli Zaretskii
2016-03-16 18:53   ` John Wiegley

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2ec5e27e-8318-2e13-7d9b-25b9ea6c74a9@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=phillip.lord@russet.org.uk \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.