From: Felipe Contreras <felipe.contreras@gmail.com>
To: "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:23:18 -0500 [thread overview]
Message-ID: <6089fc7675b95_a9ef2089d@natae.notmuch> (raw)
In-Reply-To: <87fszfafkh.fsf@angela.anarc.at>
Antoine Beaupré wrote:
> On 2021-04-23 22:44:34, Felipe Contreras wrote:
>
> [...]
>
> Well, that attempt at working with git upstream went about as bad as I
> expected. I was afraid I'd get ignored or worse, get dragged into the
> naming debate.
>
> Seems I got both, amazingly enough. I guess that I'll take that as a
> "no, not welcome here" and move on...
Do not take my response as representative of the views community.
I do believe there's value in your patch, I'm just not personally
interested in exploring it. I don't see much value in renaming branches,
especially on a distributed SCM where the names are replicated in
dozens, potentially thousands of repositories. But that's just me.
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2021-04-29 0:25 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 [this message]
2021-04-24 18:24 ` brian m. carlson
2021-04-29 0:28 ` Felipe Contreras
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=6089fc7675b95_a9ef2089d@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=anarcat@debian.org \
--cc=git@vger.kernel.org \
/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).