Re: [PATCH 0/3] making --first-parent imply -m

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 28, 2020, 16:48 UTC
Message-ID: <xmqqeeovegbv.fsf@gitster.c.googlers.com>
In-Reply-To: <20200728163617.GA2649887@coredump.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 9 quoted lines

> For some projects, it's useful to walk the first parent history, looking
> at each merge commit as a normal commit introducing all of the changes
> no its side branch. E.g.:
>
>   git log --first-parent -m -Sfoo -p
>
> might show you the topic or pull request that introduced code "foo". But
> I quite often forget to add "-m", and get confused that it doesn't
> return any results.

Yes. I agree that --first-parent should imply -m when combined with diff options like -p, --raw, etc. I am not sure if -m should kick in without any diff options, though. Doesn't it have side effects?

Thanks.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.