Re: [trinity-devel] Package naming

to understand A challenge with using the date is GIT is a moving target. Any version method used represents a snapshot moment of the repository. The GIT shortlog version better represents that snapshot moment than a date. A person could update a local repository but build a package set a week later. In that case the date would be incorrect. If there was a way to pull a date from within the sources then a date could provide a better snapshot representation of the sources. But all Trinity packagers would need to use the same mechanism to pull the date to be consistent with one another. Darrell --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting