all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: p.stephani2@gmail.com, emacs-devel@gnu.org
Subject: Re: Cherrypicking commit e08ed2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26
Date: Fri, 16 Mar 2018 16:04:10 +0200	[thread overview]
Message-ID: <83sh90p15x.fsf@gnu.org> (raw)
In-Reply-To: <87r2oksakz.fsf@gmx.de> (message from Michael Albinus on Fri, 16 Mar 2018 09:12:28 +0100)

> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: p.stephani2@gmail.com,  emacs-devel@gnu.org
> Date: Fri, 16 Mar 2018 09:12:28 +0100
> 
> This raises the question how we determine patches to be backported to
> Emacs 26.2. I have no idea, but going through all closed bugs and/or all
> commits to the master branch.

Maybe we should have a file in admin that would list such commits.  Or
maybe we should have a special phrase in the commit log message.



  reply	other threads:[~2018-03-16 14:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 18:34 Cherrypicking commit e08de2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26 Philipp Stephani
2018-03-15 19:07 ` Eli Zaretskii
2018-03-15 19:37   ` Philipp Stephani
2018-12-25 16:02     ` Philipp Stephani
2018-12-25 17:24       ` Eli Zaretskii
2019-01-02 13:03         ` Philipp Stephani
2018-03-15 19:48   ` Cherrypicking commit e08ed2bae2a8e91c0245259dfcbfdca1d191a119 " John Wiegley
2018-03-15 20:02     ` Eli Zaretskii
2018-03-15 23:54       ` John Wiegley
2018-03-16  3:41         ` Eli Zaretskii
2018-03-16  5:07           ` John Wiegley
2018-03-16  8:12             ` Michael Albinus
2018-03-16 14:04               ` Eli Zaretskii [this message]
2018-03-16 14:20                 ` Michael Albinus

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=83sh90p15x.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=p.stephani2@gmail.com \
    /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.