What does it mean to have multiple upstream tracking branches?

 Hi,

In my recent attempt to create a "simple" branch.autosetupmerge option, I have repeatedly been confused by the enforced rules around what is and isn't valid for the branch.<name>.merge and branch.<name>.remote configs.

Until Josh Steadman's recent work on --track=inherit, the "automatic" addition of branch.<name>.merge could only ever result in a single entry.

Now we support multiple entries being added as a perpetuation of an existing branch's setup - but what does it *mean*? I could understand if the idea was to have transparent tracking across multiple remotes that are supposed to have the same content (eg a single server set up over multiple protocols), but that does not appear to be possible - branch.<name>.remote can only have one value.

Is there any documentation (or could someone provide pointers) as to when multiple branch.<name>.merge values can make sense and what that means / what it does?

Thanks, Tao