On Thursday, July 19, 2012 12:10:35 PM UTC-7, Dan Drake wrote: > > Just a thought: it would be nice if we could somehow get "hg blame" to > annotate the file using Sage versions. Knowing that the line was changed > in changeset 17129 is useful, but what I *really* wanted to know was the > first released version of Sage (including alphas, beta, release > candidates) included that change. >
Good question! hg's language for describing changesets is remarkably flexible. I took a look at http://www.selenic.com/mercurial/hg.1.html#revisions and the trick seems to be: hg log -r "limit(descendants(17129) and tag(),1)" so with that in place, you could take the output of "hg blame", look up tags for the revisions showing up there and substitute them in the output. In practice, though, I think it's probably enough to know when each patch to the file got published and this seems to do the trick for that: hg log --template "changeset:\t{rev}:{node}\nuser:\t\t{author}\ndate:\t\t{date|rfc822date}\nsummary:\t{desc}\npublished:\t{latesttag}\n\n" m4ri.pxd -- -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
