On Thu, 04 Mar 2010 09:22:09 -0800, Garrett D'Amore <garr...@damore.org> wrote: > On 03/ 4/10 05:03 AM, Dennis Clarke wrote: >> >> Sorry for the long winding email but I am really thinking that the header >> data is nice to have around and still useful. Is there some easy way to >> get that data back ( an awesome awk/sed/grep script ) or is it lost >> forever? >> >> > > Lost forever. But ultimately, the data was not as useful as you think > it was. SCCS ids were only unique in the code branch that they were > part of -- S10 version 1.134 might be very different from the same file > versioned 1.134 on Solaris Nevada or Solaris 8. > > Hg doesn't version files separately like SCCS under Teamware did. We > *could* build hg version numbers (for the entire repository) into ELF > binaries, or even stash them into headers via #ident, but it turns out > that this is a major bit of trouble (it forces binaries to be different > that might otherwise be identical, for example), and so we have decided > not to do it. >
If you think it would be worthwhile, the ID of the last changeset that modified the file could be used instead. You coujld also include a date as in the SCCS-style version info. -Albert _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
