Lev <leventelist@xxxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html