[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: make change-history on non-master branches
From: |
Eli Zaretskii |
Subject: |
Re: make change-history on non-master branches |
Date: |
Wed, 18 Nov 2015 21:22:46 +0200 |
> From: Glenn Morris <address@hidden>
> Date: Wed, 18 Nov 2015 13:28:08 -0500
> Cc: address@hidden, address@hidden
>
> Quite possibly. I don't know exactly what happens if the commit hash
> from the ChangeLog.2 footer were to get merged between branches.
>
> I don't know how to solve this problem, but it seems to me that it needs
> to be solved, and the more master and emacs-25 diverge, the worse it
> gets.
>
> (All I can say, which I know isn't helpful, is that if the corrections
> were stored on a per commit-basis, this issue would not arise, AFAICS.)
Btw, one other issue that needs to be taken care of is
admin/authors.el, which needs to be taught about top-level ChangeLog.2
file.
- Re: Future release schedules (was: make change-history on non-master branches), (continued)
- Re: Future release schedules (was: make change-history on non-master branches), Eli Zaretskii, 2015/11/20
- Re: Future release schedules, John Wiegley, 2015/11/20
- Re: Future release schedules (was: make change-history on non-master branches), Artur Malabarba, 2015/11/20
- Re: Future release schedules (was: make change-history on non-master branches), Artur Malabarba, 2015/11/20
- Re: Future release schedules (was: make change-history on non-master branches), Eli Zaretskii, 2015/11/20
- Re: Future release schedules (was: make change-history on non-master branches), Eli Zaretskii, 2015/11/20
- Re: Future release schedules, John Wiegley, 2015/11/20
- Re: Future release schedules, Eli Zaretskii, 2015/11/20
- Re: Future release schedules, John Wiegley, 2015/11/20
- Re: Future release schedules, Eli Zaretskii, 2015/11/21
- Re: make change-history on non-master branches,
Eli Zaretskii <=
- Re: make change-history on non-master branches, Glenn Morris, 2015/11/18