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

Re: Weird merge records

From
DSDan Stromberg <strombrg@gmail.com>
Date
May 8, 2023, 16:53 UTC
Message-ID
<CAOvKW57WdwNoYXJyebMf-V4mQBz5CjvD=qhGxtht_2YKuygL1g@mail.gmail.com>
In-Reply-To
<64590f5430b36_79d229439@chronos.notmuch>

On Mon, May 8, 2023 at 8:03 AM Felipe Contreras <felipe.contreras@gmail.com> wrote:

Show 5 quoted lines
> > You seem to be implying that I shouldn't use 'git pull --rebase
> > upstream "$branch"'.
>
> If you know what you are doing, then do whatever you want. `git pull --rebase
> upstream $branch` is fine, if you know what that does.
I consider myself a git neophyte.  It's a large topic.
> I would just keep in mind that `git pull` wasn't meant to merge your changes to
> upstream, it was meant to merge $branch to your integration branch.
I see.
> > If that's the case, what would you recommend?
>
> I would recommend `git fetch` + `git rebase` (or merge). If you are explicit
> about what you want to do, surprises are minimized.
Might that look like:
        git checkout "$branch"
        git fetch upstream
        git rebase "$branch"
        git push origin "$branch"
?
Thanks!
Previous: Felipe ContrerasNext: Felipe Contreras
Message 6 of 8 in “Weird merge records”
  1. Dan StrombergApr 28, 2023
  2. Thomas GuyotMay 6, 2023
  3. Felipe ContrerasMay 7, 2023
  4. Dan StrombergMay 8, 2023
  5. Felipe ContrerasMay 8, 2023
  6. Dan StrombergMay 8, 2023
  7. Felipe ContrerasMay 8, 2023
  8. Dan StrombergMay 8, 2023

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.