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

Re: [PATCH v2] Revamp git-cherry(1)

From
Thomas Rast <tr@thomasrast.ch>
Date
Nov 22, 2013, 19:37 UTC
Message-ID
<87li0gi5xx.fsf@linux-k42r.v.cablecom.net>
In-Reply-To
<xmqqa9gw1bne.fsf@gitster.dls.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
> We are listing those that need to be added to the upstream with "+",
> while listing those that can be dropped from yours if you rebase
> with "-".  Hinting the rationale behind the choice of "+/-"
> somewhere may help as a mnemonic to the readers (see below).
[...]
Show 10 quoted lines
> And the earlier "why +/-" could be done after this picture,
> perhaps like:
>
> 	Here, we see that the commits A and C (marked with `-`) can
> 	be dropped from your `topic` branch when you rebase it on
> 	top of `origin/master`, while the commit B (marked with `+`)
> 	still needs to be kept so that it will be sent to be applied
> 	to `origin/master`.
>
> or somesuch?

Good idea, thanks. Will integrate this more "what still needs to be integrated"-minded wording into a v3.

-- 
Thomas Rast
tr@thomasrast.ch
Previous: Junio C HamanoNext: Junio C Hamano
Message 9 of 10 in “Revamp git-cherry(1)”
  1. Revamp git-cherry(1)Thomas Rast, Nov 21, 2013
  2. Jeff KingNov 21, 2013
  3. Thomas RastNov 21, 2013
  4. Junio C HamanoNov 21, 2013
  5. Thomas RastNov 21, 2013
  6. Junio C HamanoNov 21, 2013
  7. Revamp git-cherry(1)Thomas Rast, Nov 22, 2013
  8. Junio C HamanoNov 22, 2013
  9. Thomas RastNov 22, 2013
  10. Junio C HamanoNov 22, 2013

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.