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

Re: [RFC PATCH] Option to allow cherry-pick to skip empty commits

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 23, 2017, 18:15 UTC
Message-ID
<xmqqd1fdtzgv.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAOxFTczut_CGGxmbrVFzhn_o4=StTOY6N1mEAw75Ro2Q4tzWgQ@mail.gmail.com>
Giuseppe Bilotta <giuseppe.bilotta@gmail.com> writes:
> By the way, I noticed going over the code that the -allow options are
> not stored, so that in case of interruption they will be reset, is
> this intentional or a bug?

I do not know offhand, but given the history of the two commands, I would guess it was a bug simply overlooked when people bolted "a series of commits" mode onto these commands that originally worked only on a single commit.

Previous: Giuseppe BilottaNext: Giuseppe Bilotta
Message 4 of 7 in “Option to allow cherry-pick to skip empty commits”
  1. Option to allow cherry-pick to skip empty commitsGiuseppe Bilotta, Jan 21, 2017
  2. Junio C HamanoJan 22, 2017
  3. Giuseppe BilottaJan 23, 2017
  4. Junio C HamanoJan 23, 2017
  5. Giuseppe BilottaJan 23, 2017
  6. Junio C HamanoJan 23, 2017
  7. Giuseppe BilottaJan 23, 2017

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.