Re: cherry-pick merge commit with log message populated

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: cherry-pick merge commit with log message populated
From: Junio C Hamano <gitster@xxxxxxxxx>
Date: Thu, 01 Aug 2019 13:24:00 -0700
Cc: git@xxxxxxxxxxxxxxx
In-reply-to: <CABUeae8EBzPSM1KrZTMiGj=6F3iyxeXXbqUNMf2p_LfPkqcfnA@mail.gmail.com> (Mateusz Loskot's message of "Thu, 1 Aug 2019 21:49:30 +0200")
References: <CABUeae8EBzPSM1KrZTMiGj=6F3iyxeXXbqUNMf2p_LfPkqcfnA@mail.gmail.com>
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)

Mateusz Loskot <mateusz@xxxxxxxxxx> writes:

> Is there any other way, without remembering to `git merge` with `--log`?

"git config merge.log true"?

Follow-Ups:
- Re: cherry-pick merge commit with log message populated
  - From: Mateusz Loskot

References:
- cherry-pick merge commit with log message populated
  - From: Mateusz Loskot

Prev by Date: What's cooking in git.git (Aug 2019, #01; Thu, 1)
Next by Date: Re: Support for --stdin-paths in commit, add, etc
Previous by thread: cherry-pick merge commit with log message populated
Next by thread: Re: cherry-pick merge commit with log message populated
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux