all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: emacs-devel@gnu.org
Subject: Re: New test files in emacs-25 branch
Date: Fri, 04 Dec 2015 10:32:27 +0200	[thread overview]
Message-ID: <83a8pqipgk.fsf@gnu.org> (raw)
In-Reply-To: <878u5bxihw.fsf@russet.org.uk>

> From: phillip.lord@russet.org.uk (Phillip Lord)
> Cc: <emacs-devel@gnu.org>
> Date: Thu, 03 Dec 2015 22:41:31 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> >> I guess this crossed my mind sometime after I offered to move all the
> >> file locations. Probably it would have made sense to leave things till
> >> after the emacs-25.
> >
> > It wouldn't have mattered.  Emacs 25.1 is not going to be the only
> > version delivered from the emacs-25 branch.
> 
> Really? I assumed 25.2 was going to fork from current master.

It could be, but given our previous history, it rarely happens.  The
master branch gets many new features very quickly, so making a minor
release from it no longer makes sense.  That is the price we pay for
not freezing master when a release is being prepared.

> I was thinking of the situation where a new file is added to
> emacs-25, merged to master and then more tests are added (i.e. the
> new files is subsequently updated). As you say, the addition of a
> file into two places is not so bad. But it would be nice if
> subsequent updates to the file worked.

I don't expect them to work.



      reply	other threads:[~2015-12-04  8:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-03 11:37 New test files in emacs-25 branch Eli Zaretskii
2015-12-03 12:53 ` Artur Malabarba
2015-12-03 13:20   ` Eli Zaretskii
2015-12-03 17:52 ` Phillip Lord
2015-12-03 20:13   ` Eli Zaretskii
2015-12-03 22:41     ` Phillip Lord
2015-12-04  8:32       ` Eli Zaretskii [this message]

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=83a8pqipgk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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.