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

Re: [PATCH] rebase: use @{upstream} if no upstream specified

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 10, 2011, 02:25 UTC
Message-ID
<7voc6k62xq.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1297302842-11296-1-git-send-email-martin.von.zweigbergk@gmail.com>
Martin von Zweigbergk <martin.von.zweigbergk@gmail.com> writes:
> 'git rebase' without arguments is currently not supported. Make it
> default to 'git rebase @{upstream}'. That is also what 'git pull
> [--rebase]' defaults to, so it only makes sense that 'git rebase'
> defaults to the same thing.

Not that I am fundamentally opposed to the proposed change, but the above is not a very convincing argument, when the corresponding change to "git merge" is just started getting discussed.

On top of what commit does this patch apply, by the way?
Previous: Martin von ZweigbergkNext: Martin von Zweigbergk
Message 11 of 12 in “rebase: use @{upstream} if no upstream specified”
  1. rebase: use @{upstream} if no upstream specifiedMartin von Zweigbergk, Feb 8, 2011
  2. Sverre RabbelierFeb 8, 2011
  3. Martin von ZweigbergkFeb 8, 2011
  4. Sverre RabbelierFeb 8, 2011
  5. Jonathan NiederFeb 8, 2011
  6. Martin von ZweigbergkFeb 9, 2011
  7. Martin von ZweigbergkFeb 9, 2011
  8. Jonathan NiederFeb 9, 2011
  9. Martin von ZweigbergkFeb 10, 2011
  10. rebase: use @{upstream} if no upstream specifiedMartin von Zweigbergk, Feb 10, 2011
  11. Junio C HamanoFeb 10, 2011
  12. Martin von ZweigbergkFeb 10, 2011

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.