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

Re: why "git rebase" searching the duplicate patches in <upstream branch> rather than in <new base branch>?

From
Sergey Organov <sorganov@gmail.com>
Date
Jul 20, 2021, 16:44 UTC
Message-ID
<87y2a19bp9.fsf@osv.gnss.ru>
In-Reply-To
<xmqqczrdhu9q.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
> Sergey Organov <sorganov@gmail.com> writes:
>
[...]
Show 6 quoted lines
>
>> I don't actually like this.
>
> You do not have to ;-) because I was not suggesting to change any
> existing behaviour.  It was merely me thinking aloud, how I might
> do the feature if I were designing it from scratch now.

Yeah, I've noticed the absence of [PATCH] ;-) and was just thinking aloud myself as well.

Thanks,
-- 
Sergey Organov
Previous: Junio C HamanoNext: Andy Zhang
Message 6 of 7 in “why "git rebase" searching the duplicate patches in <upstream branch> rather than in <new base branch>?”
  1. Andy ZhangJul 19, 2021
  2. Felipe ContrerasJul 19, 2021
  3. Junio C HamanoJul 19, 2021
  4. Sergey OrganovJul 20, 2021
  5. Junio C HamanoJul 20, 2021
  6. Sergey OrganovJul 20, 2021
  7. Andy ZhangAug 1, 2021

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.