From: Junio C Hamano <gitster@pobox.com>
To: Lev <leventelist@gmail.com>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: remotes
Date: Tue, 03 May 2016 13:38:22 -0700 [thread overview]
Message-ID: <xmqqshxylvwh.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160503181624.1504eb0a@laborpc> (Lev's message of "Tue, 3 May 2016 18:16:24 +0200")
Lev <leventelist@gmail.com> writes:
> I accidentally added a remote of another repository to my config file. And so I
> merged two different repositories together. Is there any real user case for
> this?
Using multiple remotes is a perfectly normal way in which you are
expected to interact with a single project with other participants.
Perhaps there is one single authoritative and canonical repository
where everybody initially clones from, and it is likely that that
repository is your "origin". Often there are cases where another
participant has a topic that is not yet ready for the mainline but
is worth considering for early adopters and/or is solid enough for
other project participants to build their work on. In such cases,
you can add the repository of that other participant as the second
remote and fetch from her.
It makes no sense if the two repositories hold histories of totally
unrelated projects, of course.
next prev parent reply other threads:[~2016-05-03 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 16:16 remotes Lev
2016-05-03 20:38 ` Junio C Hamano [this message]
2016-05-03 23:36 ` remotes Kovacs Levente
2016-05-03 23:47 ` remotes Stefan Beller
2016-05-04 7:04 ` remotes Junio C Hamano
2016-05-04 8:11 ` remotes 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=xmqqshxylvwh.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=leventelist@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.