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

Re: [PATCH v2] Add push --set-upstream

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 16, 2010, 01:10 UTC
Message-ID
<7vhbqmn9c4.fsf@alter.siamese.dyndns.org>
In-Reply-To
<be6fef0d1001151653o7ba2cf7et8875eaf4333fc15a@mail.gmail.com>
Tay Ray Chuan <rctay89@gmail.com> writes:
Show 22 quoted lines
> Hi,
>
> On Sat, Jan 16, 2010 at 8:06 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> Nanako Shiraishi <nanako3@lavabit.com> writes:
>>
>>> Quoting Junio C Hamano <gitster@pobox.com>
>>>
>>>> Junio C Hamano <gitster@pobox.com> writes:
>>>>
>>>>>         # Ok let's do it for real.
>>>>>         git push    --track there this
>>>>
>>>> Ugh; s/--track/--set-upstream/, of course.
>>>
>>> How can I use this to say I want to use 'pull --rebase'?
>>
>> I dunno; "git push --set-upstream=rebase", perhaps?
>
> how about --setup-merge and --setup-rebase?
>
> After all, there's already the config called branch.autosetupmerge and
> branch.autosetuprebase.

Do you mean Ilari's patch already sets up branch.name.rebase for people with branch.autosetuprebase true?

If so, it might be better to keep "--set-upstream" as is, and have a way to countermand that "autosetuprebase" default.

Previous: Sverre RabbelierNext: Junio C Hamano
Message 10 of 15 in “Add push --set-upstream”
  1. Add push --set-upstreamIlari Liusvaara, Jan 15, 2010
  2. Junio C HamanoJan 15, 2010
  3. Junio C HamanoJan 15, 2010
  4. Nanako ShiraishiJan 16, 2010
  5. Junio C HamanoJan 16, 2010
  6. Tay Ray ChuanJan 16, 2010
  7. Sverre RabbelierJan 16, 2010
  8. Tay Ray ChuanJan 16, 2010
  9. Sverre RabbelierJan 16, 2010
  10. Junio C HamanoJan 16, 2010
  11. Junio C HamanoJan 16, 2010
  12. Tay Ray ChuanJan 16, 2010
  13. Nanako ShiraishiJan 16, 2010
  14. Tay Ray ChuanJan 16, 2010
  15. Rudolf PolzerJan 16, 2010

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.