Shawn M Emery wrote: > In the near future it would be nice to have some form of keyword > expansion whether in one form or another. If everyone is in agreement > then we may want to consider the keyword extension for mercurial which > allows fairly easy interface to expand and contract keywords:
One of the benefits of moving to Mercurial is that we can remove (or at least, massively decrease) our reliance on SCCS keywords that very, very frequently have absolutely no relationship to reality. Case in point: I had to make some changes to one of the files that goes into the scsi_vhci module. Not scsi_vhci.c itself, but a related file. Since the SCCS %I% tag was not changed in scsi_vhci.c, it was very difficult to figure out (from modinfo output, eg) whether the customer was actually running my version of the binary. In addition, if you search the scm-migration and tools-discuss archives you'll see that this issue has been beaten to death already. I think you'll find that the people on this mailing list are not in favour of what you suggest. James C. McPherson -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog
