From: Elijah Newren <newren@gmail.com>
To: Shourya Shukla <shouryashukla.oo@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [PATCH v4 2/4] gitfaq: changing the remote of a repository
Date: Wed, 29 Apr 2020 09:17:43 -0700 [thread overview]
Message-ID: <CABPp-BFJe81XD6Sd0OPoLGG5u2Vr4xoQrM2N=20eLscw0r8oXw@mail.gmail.com> (raw)
In-Reply-To: <20200429093811.8475-2-shouryashukla.oo@gmail.com>
On Wed, Apr 29, 2020 at 2:38 AM Shourya Shukla
<shouryashukla.oo@gmail.com> wrote:
>
> Add issue in 'Common Issues' section which addresses the problem of
> changing the remote of a repository, covering various cases in which
> one might want to change the remote and the ways to do the same.
>
> Signed-off-by: Shourya Shukla <shouryashukla.oo@gmail.com>
> ---
> Documentation/gitfaq.txt | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/Documentation/gitfaq.txt b/Documentation/gitfaq.txt
> index b1e758ffd1..7d294306f9 100644
> --- a/Documentation/gitfaq.txt
> +++ b/Documentation/gitfaq.txt
> @@ -232,6 +232,17 @@ I asked Git to ignore various files, yet they are still tracked::
> it is advised to use `git rm --cached <file>`as well as make
> the file pattern is mentioned in the '.gitignore'.
>
> +[[changing-remote-of-the-repository]]
> +I want to change the remote of my repository. How do I do that?::
> + A remote is an identifier for a location to which Git pushes your
> + changes as well as fetches any new changes from (if any). There
> + might be different circumstances in which one might need to change
> + the remote URL (see linkgit:git-remote[1]). To change the remote URL
> + one may use: git remote set-url <name> <newurl>
> ++
> +One can list the remotes of a repository using `git remote -v` command.
> +The default name of a remote is 'origin'.
Looks good to me. :-)
next prev parent reply other threads:[~2020-04-29 16:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 9:38 [PATCH v4 1/4] gitfaq: files in .gitignore are tracked Shourya Shukla
2020-04-29 9:38 ` [PATCH v4 2/4] gitfaq: changing the remote of a repository Shourya Shukla
2020-04-29 16:17 ` Elijah Newren [this message]
2020-04-29 17:01 ` Junio C Hamano
2020-04-29 9:38 ` [PATCH v4 3/4] gitfaq: shallow cloning " Shourya Shukla
2020-04-29 16:00 ` Elijah Newren
2020-05-02 5:00 ` Shourya Shukla
2020-04-29 17:09 ` Junio C Hamano
2020-05-02 6:13 ` Shourya Shukla
2020-05-04 16:06 ` Junio C Hamano
2020-05-05 12:26 ` Derrick Stolee
2021-05-06 2:49 ` dyrone teng
2020-04-29 9:38 ` [PATCH v4 4/4] gitfaq: fetching and pulling " Shourya Shukla
2020-04-29 15:56 ` Elijah Newren
2020-04-29 17:19 ` Junio C Hamano
2020-05-02 6:57 ` Shourya Shukla
2020-05-02 19:00 ` Elijah Newren
2020-05-03 1:03 ` Junio C Hamano
2020-04-29 16:16 ` [PATCH v4 1/4] gitfaq: files in .gitignore are tracked Elijah Newren
2020-05-02 6:36 ` Shourya Shukla
2020-04-29 16:55 ` Junio C Hamano
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='CABPp-BFJe81XD6Sd0OPoLGG5u2Vr4xoQrM2N=20eLscw0r8oXw@mail.gmail.com' \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sandals@crustytoothpaste.net \
--cc=shouryashukla.oo@gmail.com \
/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.
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 NNTP newsgroup(s).