Git Checkout tracking behavior with <start_point>?

[Cyrus Vafadari <cvafadari@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