On Mon, Jun 4, 2012 at 8:02 PM, Andy Isaacson <adi@xxxxxxxxxxxx> wrote: > On Sat, Jun 2, 2012 at 2:49 AM, Alexandre Bique > <bique.alexandre@xxxxxxxxx> wrote: >> On Fri, Jun 1, 2012 at 1:59 AM, Andy Isaacson <adi@xxxxxxxxxxxx> wrote: >> > +.BR CLOCK_MONOTONIC_COARSE " (since Linux 2.6.32; Linux-specific)" >> > +.\" Added in commit da15cfdae03351c689736f8d142618592e3cebc3, John Stultz, Aug 19 2009 >> >> Is it necessary to specify the commit rev? > > Speaking as a git user, it's much more helpful to provide the commitID > than to just provide committer+date as was done for other items in > this file. It allows "git tag --contains da15cfdae" to find out what > release it was merged in, for example. > > Is there any downside to having the commit hash in the comment? I agree with you, it is convenient to have the commit revision when you need to dig into Linux source code. -- Alexandre Bique -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
