From: Felipe Contreras <felipe.contreras@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Antoine Beaupré" <anarcat@debian.org>, git@vger.kernel.org
Subject: Re: how to rename remote branches, the long way
Date: Wed, 28 Apr 2021 19:28:49 -0500 [thread overview]
Message-ID: <6089fdc1bfc0f_a9ef2081e@natae.notmuch> (raw)
In-Reply-To: <YIRiSJDem/JaBHuN@camp.crustytoothpaste.net>
brian m. carlson wrote:
> On 2021-04-24 at 03:44:34, Felipe Contreras wrote:
> > 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.
That's fine, you don't need to find it useful.
> 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.
What is "in this way"? Proposing another solution more people (including
me) might find simpler, and more viable?
> 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 wasn't rude. You are free to disagree.
> [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.
I never claimed otherwise.
It's perfectly fine for two people to work on two approaches to solve
the same problem.
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2021-04-29 0:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 0:22 how to rename remote branches, the long way Antoine Beaupré
2021-04-24 1:08 ` Felipe Contreras
2021-04-24 1:12 ` Antoine Beaupré
2021-04-24 3:44 ` Felipe Contreras
2021-04-24 15:05 ` Antoine Beaupré
2021-04-29 0:23 ` Felipe Contreras
2021-04-24 18:24 ` brian m. carlson
2021-04-29 0:28 ` Felipe Contreras [this message]
2021-04-24 17:38 ` brian m. carlson
2021-04-24 18:03 ` Antoine Beaupré
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6089fdc1bfc0f_a9ef2081e@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=anarcat@debian.org \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).