git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] name_rev: add support for --cherry-picks

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 26, 2018, 19:01 UTC
Message-ID
<xmqqr2jpq0s1.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20180726153714.GX1934745@devbig577.frc2.facebook.com>
Tejun Heo <tj@kernel.org> writes:
> I should have explained the use case better.

No, you did not need to. I was not saying the feature is not useful. I was only saying that "explain where in the history X sits" command (i.e. "name-rev X" and "describe X") did not look like a good place to have that feature.

Show 7 quoted lines
>   Upstream, it's v4.17-rc1
>     Backported and released through v4.16-prod-r2
>       Also backported to v4.16-prod-r1 (cuz the fix happened while r1 was going through rc's)
>
> So, it extends the description of how the original commit is released
> (or given name) so that releases through cherry-picks are also
> included.

Perhaps. I am not yet 100% convinced, but having a less hard time trying to convince myself now ;-)

Thanks.
Previous: Tejun HeoNext: Jeff King
Message 5 of 8 in “name_rev: add support for --cherry-picks”
  1. name_rev: add support for --cherry-picksTejun Heo, Jul 26, 2018
  2. name_rev: add support for --cherry-picksTejun Heo, Jul 26, 2018
  3. Junio C HamanoJul 26, 2018
  4. Tejun HeoJul 26, 2018
  5. Junio C HamanoJul 26, 2018
  6. Jeff KingJul 27, 2018
  7. Tejun HeoJul 27, 2018
  8. Junio C HamanoJul 27, 2018

Read the whole thread, see it on lore, or plain text.

$ 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.