Now that OVS is upstream, I'm changing the strategy a little for tracking changes to the kernel.org tree. Previously there was a lot a churn as things like compatibility code were stripped out but now it's mostly just about keeping things in sync.
The address of the tree is the same: git://git.kernel.org/pub/scm/linux/kernel/git/jesse/openvswitch.git There are two branches of general interest: 'master' and 'fixes' which correspond to 'net-next' and 'net' respectively, which is to say the first is for large features destined for two releases out and the second for bug fixes for this cycle. Currently, everything is in sync with the OVS tree so neither of those branches contains anything other than upstream work. Normal development should continue on the OVS tree, as it is today. Small things, I'll just pick up and apply to the upstream tree directly. Larger features, I'll likely ask the submitter to provide a cross-port once it is in the OVS tree. Unless I ask, you can assume that I'll take care of it. When doing cross-ports, please minimize any extraneous changes to help keep things consistent. Of course, this only applies to things that are actually upstream so, for example, changes that only affect compatibility code don't need to be cross-ported. Changes that are made upstream I'll bring over the OVS tree. _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
