From: Ben Knoble <ben.knoble@gmail•com>
To: Michael Woodard <mwoodard@metropolis•io>
Cc: git@vger•kernel.org
Subject: Re: git remote rename command help
Date: Sat, 1 Nov 2025 19:45:46 -0400 [thread overview]
Message-ID: <54E0F3F7-7CB6-4963-BA95-AA60E76BCF44@gmail.com> (raw)
In-Reply-To: <CAJ6i6FDqj0yCymuGd+f89XQvTLGRj3nVC-36Z4tbJfwNRKSt+w@mail.gmail.com>
> Le 31 oct. 2025 à 21:51, Michael Woodard <mwoodard@metropolis•io> a écrit :
>
> Hello,
>
> I entered the command "git remote rename Old_Name New_Name" but it
> appears to only have affected the Local Repo I am working with. Other
> requests or connections to remote repo still see the Old_Name. What am
> I missing?
>
> Michael Woodard | SP+ | A Metropolis Company | Manager, IT Operations
>
> Mobile: 251.463.2791
What, precisely, do you mean by “other connections”? A remote name is a local-only concept (effectively a pointer to a resource locator and other metadata, like a fetch refspec). If you expected this to, say, change the name of a repository on a server, that’s not really what this command does.
PS I’m surprised to see a phone number :) I expect you are inundated with spam messages (voice or text).
prev parent reply other threads:[~2025-11-01 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-01 1:38 git remote rename command help Michael Woodard
2025-11-01 23:45 ` Ben Knoble [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54E0F3F7-7CB6-4963-BA95-AA60E76BCF44@gmail.com \
--to=ben.knoble@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=mwoodard@metropolis$(echo .)io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox