| [Raster tiles][rt] | [Vector tiles][vt] | GeoJSON | virtual-dom | offline | map quality | React component | React Native | |
|---|---|---|---|---|---|---|---|---|
| google maps | + | + | good | [4 unsupported][gm-react] | [+][gm-native] | |||
| leaflet * | + | [+][ll-vt] | + | [+/-][ll-offline] | depends | [+][ll-rect] | ||
| d3 * | + | [+/-][d3-vdom] | +/- | depends | [+][d3-react] | |||
| MapboxGL | + | + | depends | [+][mb-react] | [+][mb-native] | |||
| Yandex Maps | + |
Branch A has commits (X,Y) that also need to be in Branch B. The cherry-pick operations should be done in the same chronological order that the commits appear in Branch A.
cherry-pick does support a range of commits, but if you have merge commits in that range, it gets really complicated
git checkout branch-B
git cherry-pick X
git cherry-pick Y