On 03/08/16 13:12, David Woodhouse wrote: > So please, DO NOT REBASE submissions onto the latest master. Use the > tools properly as they were designed to be used — put any non-trivial > work into a tree and send it as a pull request. Sure, send the patches > to the list for review *too*, but that shouldn't be how they actually > get in.
I support the idea. I have no input on the urgency of it. As soon as Intel leadership signs off on a merge-oriented workflow, I'll seek to adopt it immediately. (Importantly: this shall not include *github* pull requests, only pull requests sent to the mailing list, and the patches must also be on the list. I think what people frequently do is, they format the series as usual, just include the pull request (formatted with git-request-pull) in the blurb. In such cases the PATCH subject prefix can also be replaced with PULL, across the full series.) Until then, we'll have to stick with the rules that we have now. (Again, I do support the idea.) Thanks Laszlo _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
