Re: Git merge commit message issue
- From
Andrey Hsiao <andreyhsiao@gmail.com>
- Date
- Jul 6, 2015, 16:16 UTC
- Message-ID
- <CAArk4YPvO46H2HXkPyPxwirauKXYJ1qpi_GmYMh-T2xz5EdaBQ@mail.gmail.com>
- In-Reply-To
- <vpqtwths1yq.fsf@anie.imag.fr>
It was a bit sad since we use scripts to do the merge, then we can check the conflict list in the log message, and assign to separate owners to resolve them.
Would it be possible to make it as an config option?
On Tue, Jul 7, 2015 at 12:08 AM, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:
Show 23 quoted lines
> Andrey Hsiao <andreyhsiao@gmail.com> writes: > >> Dear list: >> >> In the past, when we do the merge in git, if conflicts occurred, >> when we commit, the conflict list will be appended to >> the default commit message automatically. >> >> eg: >> Conflicts: >> ....a.java >> ....b.java >> >> Today, after using Git 2.3.0 for a merge, it seems now the conflict list >> was commented out by default. > > Yes, this changed here: > > https://github.com/git/git/commit/261f315bebfa9af2d09f20211960100ff06f87cb > > -- > Matthieu Moy > http://www-verimag.imag.fr/~moy/