On Tue, May 3, 2016 at 4:36 PM, Kovacs Levente <leventelist@xxxxxxxxx> wrote: > On Tue, 03 May 2016 13:38:22 -0700 > Junio C Hamano <gitster@xxxxxxxxx> wrote: > >> 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. > > Yes, I use that feature. > >> It makes no sense if the two repositories hold histories of totally >> unrelated projects, of course. > > Would it make sense to implement some protection against these kind of > accidents? At least a question "are you sure you want to merge two > independent repositories/branches?" A recent addition is the check for unrelated histories via checking for added root commits (i.e. commits with no parent) and refusing to merge them by default. you need to pass --allow-unrelated-histories to merge. see https://kernel.googlesource.com/pub/scm/git/git/+/e379fdf34fee96cd205be83ff4e71699bdc32b18 > > Thanks, > Lev > > > -- > 73 de HA5OGL > Op.: Levente -- 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