On 10 Aug 13, Michael Hope wrote: > The next big thing for the Toolchain WG is sending patches upstream > and beginning to track patches in general. Some of the use cases are: > > * Do a change upstream in 4.7, backport it to our 4.5, and backport > it to our 4.6 when we make one > * Do a change locally, track where it lands upstream, and figure out > what we have to bring forward when we next rebase > * Track what is Linaro specific and can't go upstream so we know what > to bring forward > > I'm currently planning to use the Launchpad bug tracker and some > custom reports to manage this. It's important that we don't lose any > patches.
So git-based workflows won't benefit from this then? > Does anyone else have similar requirements, use for such a tool, or > know of tools that already cover this? It would be very useful for tracking kernel/tools deltas in the Kernel and PM WG. I know the Ubuntu Kernel team has expressed an interest in such a tool too. /Amit _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
