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

Git Checkout tracking behavior with <start_point>?

From
CVCyrus Vafadari <cvafadari@gmail.com>
Date
Nov 3, 2021, 15:08 UTC
Message-ID
<CAMd+_QCDN5UwwC=ZRcT4Y3p1x7kCQ1TEVf5321Ykx4xrhv-YOA@mail.gmail.com>
Hello all,
I'm new to this mailing list, so I hope I'm doing it right!

I am an avid user of this pattern: "git checkout -b my_branch upstream/3.2.x", using "start_point" to build my backported patch against an old feature version. But in this case, the default tracking is against 3.2.x, rather than my new feature branch. So, then, when I push I specify to update the tracking against the new branch name. There are also various default behaviors for push, which I won't enumerate here, but in the end I need to specify tracking.

I'm wondering if there is some usage/pattern I'm missing?

Or is this an opportunity to add a gitconfig for "tracking behavior" of `checkout` with start_point? If there is agreement that this could be improved with a new config, I'd be happy to open a PR.

Best, Cyrus

Next: Stefan Moch
Message 1 of 3 in “Git Checkout tracking behavior with <start_point>?”
  1. Cyrus VafadariNov 3, 2021
  2. Stefan MochNov 3, 2021
  3. Jeff KingNov 4, 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.