Den mandag den 21. oktober 2013 09.56.53 UTC+2 skrev Casper Schmidt: > > > > Den lørdag den 19. oktober 2013 10.01.47 UTC+2 skrev Peter J Weisberg: >> >> On Oct 18, 2013 12:29 PM, "Casper Schmidt" <kalle....@gmail.com> wrote: >> >> > My question is then: Is there any way to merge multiple repositories >> into a single repository but in their own branch. I have found a few >> guidelines using multiple remotes and simple merge but this merges the >> history into the master branch every time I try. Also some guidelines talk >> about merging repositories into seperate directories, but that is not >> really what we want. >> >> If I understand correctly (which I might not) , you don't actually want >> to "merge" anything. You want to fetch from multiple remotes, then make >> local branches for each of them. That's just 'git branch myNewBranch >> someRemote/master'. >> > Maybe merge is indeed the wrong term to use. I will try your suggestion > and get back later today :) >
Okay the git branch newBranch remote/master did the trick (that is not possible through SourceTree to my knowledge). What I would really like now (but it is secondary), is to avoid the master and newBranch trees/graph placed on top of each other (it makes it difficult to find the right graph once we have 15 branches on top of each other. Instead it could be nice to bind the branches together in a common parent (ie. the inital commit of master in the new repository). What is the best way to achieve this? Create a new branch from master and rebase my newBranch onto that or something else? -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
