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

Re: [PATCH] git-cherry: make <upstream> parameter optional

From
Ddemerphq <demerphq@gmail.com>
Date
Dec 30, 2008, 14:02 UTC
Message-ID
<9b18b3110812300602i3bed6ab0xc9fa7757bf7cf464@mail.gmail.com>
In-Reply-To
<200812291845.20500.markus.heidelberg@web.de>
2008/12/29 Markus Heidelberg <markus.heidelberg@web.de>:
Show 8 quoted lines
> The upstream branch <upstream> now defaults to the first tracked
> remote branch, which is set by the configuration variables
> branch.<name>.remote and branch.<name>.merge of the current branch.
>
> Without such a remote branch, the command "git cherry [-v]" fails with
> usage output as before and an additional message.
>
> Signed-off-by: Markus Heidelberg <markus.heidelberg@web.de>
FWIW: I would find this useful. Thanks for writing it.
Yves
-- 
perl -Mre=debug -e "/just|another|perl|hacker/"
Previous: Johannes SchindelinNext: Junio C Hamano
Message 5 of 7 in “git-cherry: make <upstream> parameter optional”
  1. git-cherry: make <upstream> parameter optionalMarkus Heidelberg, Dec 29, 2008
  2. Johannes SchindelinDec 30, 2008
  3. Markus HeidelbergDec 30, 2008
  4. Johannes SchindelinDec 30, 2008
  5. demerphqDec 30, 2008
  6. Junio C HamanoJan 1, 2009
  7. Markus HeidelbergJan 1, 2009

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.