I have started to put a Flow Chart together for Patch Tracking Process (very preliminary draft) , see if that is what we want and let me know what to add/modify to visualize the process at at a high level, first. Cheers, Mounir
On Fri, Aug 13, 2010 at 2:57 PM, Amit Kucheria amit.kucheria@linaro.orgwrote:
On 10 Aug 13, Nicolas Pitre wrote:
On Fri, 13 Aug 2010, Michael Hope wrote:
On Fri, Aug 13, 2010 at 7:19 PM, Amit Kucheria <
amit.kucheria@linaro.org> wrote:
So git-based workflows won't benefit from this then?
There's no particular dependence on any VC system. I will be making a report on each bzr commit to make sure there is a corresponding ticket that tracks the upstream state.
At the moment you do need a backing Launchpad ticket to record the state changes. Out of interest, can git record meta data with a commit, such as the upstream status, and modify that meta data after the commit
Yes. With a recent enough Git version, you can attach so called notes to any commit and modify them at will:
http://www.kernel.org/pub/software/scm/git/docs/git-notes.html
Nice!
/me learns something new today
/amit
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev