Re: how to rename remote branches, the long way

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Apr 24, 2021, 18:24 UTC
Message-ID: <YIRiSJDem/JaBHuN@camp.crustytoothpaste.net>
In-Reply-To: <60839422353fc_10cb9208c7@natae.notmuch>

On 2021-04-24 at 03:44:34, Felipe Contreras wrote:

Show 8 quoted lines

> I see.
> 
> That makes me think we might want a converter that translates
> (local)main -> (remote)master, and (remote)master -> (local)mail
> everywhere, so if your eyes have trouble seeing one, you can configure
> git to simply see the other... Without bothering the rest of the word.
> 
> I'll give that idea a try.

I don't believe this is a helpful response, and judging from the follow-up, neither did the OP. They're not trying to do anything dangerous, improvident, or harmful to others and they are trying to solve a problem that many people have and that is due to an inherent limitation in Git (its inability to rename remote branches easily[0]), so there's no reason to respond in this way.

There is a difference between being firm and steadfast, such as when responding to someone who repeatedly advocates an inadvisable technical approach, and being rude and sarcastic, especially to someone who is genuinely trying to improve things, and I think this crosses the line. I'd appreciate it if we could aim to avoid the latter type of response and not scare off new participants to the community right away.

I realize I also sometimes fall short of where I should be in terms of kindness on the list and elsewhere, but I hope we'll all endeavor to do better here.

[0] Regardless of how you feel about this _particular_ rename, one would want the ability to do this to preserve reflogs for _all_ remote renames, and so this would be a valuable and desirable feature to have in Git anyway.

-- 
brian m. carlson (he/him or they/them)
Houston, Texas, US