Re: Find a topic branch containing a commit

From: Duy Nguyen <pclouds@gmail.com>
Date: Jul 27, 2016, 18:07 UTC
Message-ID: <CACsJy8AuP-E1qHM_sJ4ZPpZDSk3s1KkuQOLB9B38+OUkobO11g@mail.gmail.com>
In-Reply-To: <CAGZ79kYNFoAUu+5Y0oh221UeyAB3zan_36RgrhZnSi19Oe2vcA@mail.gmail.com>

On Wed, Jul 27, 2016 at 8:02 PM, Stefan Beller <sbeller@google.com> wrote:

Show 12 quoted lines

> On Wed, Jul 27, 2016 at 10:50 AM, Stefan Beller <sbeller@google.com> wrote:
>>>
>>> PS. Sometimes I wish we could optionally save cover letter in the
>>> merge commit. Sometimes the "big plan" is hard to see by reading
>>> individual commit messages.
>>> --
>
> I had this wish, too. That makes a lot of sense for merge commits,
> although it doesn't work well with our current workflow I would presume,
> because the merge commit happens at a different time than when Junio
> picks up a patch series. And in the mean time, where would we
> store the cover letter information to not get lost?

We have config branch.xxx.description for that. If we teach git-am to pick up (a selected portion of) the cover letter and save it in branch.xxx.description (or even a new key like branch.xxx.mergeMsg) then nothing is lost.

-- 
Duy