[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Cherrypicking commit e08ed2bae2a8e91c0245259dfcbfdca1d191a119 onto e
|
From: |
Eli Zaretskii |
|
Subject: |
Re: Cherrypicking commit e08ed2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26 |
|
Date: |
Fri, 16 Mar 2018 16:04:10 +0200 |
> From: Michael Albinus <address@hidden>
> Cc: address@hidden, address@hidden
> 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.
- Cherrypicking commit e08de2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26, Philipp Stephani, 2018/03/15
- Re: Cherrypicking commit e08de2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26, Eli Zaretskii, 2018/03/15
- Re: Cherrypicking commit e08de2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26, Philipp Stephani, 2018/03/15
- Re: Cherrypicking commit e08ed2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26, John Wiegley, 2018/03/15
- Re: Cherrypicking commit e08ed2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26, Eli Zaretskii, 2018/03/15
- Re: Cherrypicking commit e08ed2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26, John Wiegley, 2018/03/15
- Re: Cherrypicking commit e08ed2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26, Eli Zaretskii, 2018/03/15
- Re: Cherrypicking commit e08ed2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26, John Wiegley, 2018/03/16
- Re: Cherrypicking commit e08ed2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26, Michael Albinus, 2018/03/16
- Re: Cherrypicking commit e08ed2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26,
Eli Zaretskii <=
- Re: Cherrypicking commit e08ed2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26, Michael Albinus, 2018/03/16