| From: Lennart Sorensen <[email protected]> | On Fri, May 08, 2015 at 11:38:57AM -0400, Paul Wouters wrote: | > >To Lennard's idea, I'm not sure we can rely on modification dates. | > | > Or the date specified in CHANGES of the release. | | Yeah I don't trust modification dates either, but anything is better | than the current date. Something from CHANGES sounds great. Something | consistent that actually indicates the age of the code is what makes | sense. Manually editing dates sucks and is error prone for sure.
SCCS and RCS had ways of branding a version or date into the text of a file when it was checked in. That was good because it reflected when a change happened. Does GIT have anything like that? I'd guess that git hooks could do the job, but I don't know how easily or well. _______________________________________________ Swan-dev mailing list [email protected] https://lists.libreswan.org/mailman/listinfo/swan-dev
