> Another benefit of a merge-queue branch is testing and verifying that > multiple patches play well together before actually hitting trunk. > For multiple big branches this is even more important.
Currently blocking on http://support.github.com/discussions/feature-requests/560-two-forks-of-a-single-repo If this will not be resolved (quite likely) then there will be less convenience and GitHub goodness (e.g. "send pull request") -- as of now, manually adding django-mergequeue as a remote to an existing fork looks like the only option. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
