Am Donnerstag, 23. April 2015, 11:14:25 schrieb Daniel Hahler: > James McCoy wrote: > > If people are just going to rebase their patches, then there's no > > problem. If instead they want to merge future Vim development into > > their existing branches, then the lack of a shared history is a > > problem. > > Yes, the problem is basically that there would be no common history > between the original (mirror) remote and the new one. > This would also make rebasing more difficult already (as in "git rebase"),
Yes, more difficult, but this only means adding one option to the rebase command. > and you would have to manually apply the patches (via "git am"). No, you do not have to use "git am", but can use rebase like this: git rebase --onto newbase curbase Markus -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
