Hi Ben, On 4/13/13, Ben Hutchings <ben@xxxxxxxxxxxxxxx> wrote: > I notice that where a commit is cherry-picked cleanly on a stable > branch, like 6b90466cfec2a2fe027187d675d8d14217c12d82, your script finds > the corresponding commit on the stable branch. This is useful. > > But where some backporting changes are needed, such as for > f01fc1a82c2ee68726b400fadb156bd623b5f2f1, which became > 8ebfe28181b02766ac41d9d841801c146e6161c1 on the 3.2.y branch, the > corresponding commit isn't found. > > It should be possible to find such backported commits based on a simple > regex search over the commit message: I took a more aggressive approach. I decided to look for 40 length character hashes in the comment and patch of the commit. if the hash is in the database of commits I maintain, then I display it. if not, it is ignored. You can revisit the output of that commit: http://o.cs.uvic.ca:20810/perl/cid2.pl?cid=8ebfe28181b02766ac41d9d841801c146e6161c1 This means I am able to show when a commit is referenced by another one, and the commits that a commit references. hopefully this solves the use-case you described. The commit logs are being scanned as I write this. It should be done in a couple of hours. --dmg --- Daniel M. German http://turingmachine.org -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html