On 4/16/07, Theodore Tso <tytso@xxxxxxx> wrote:
Simple, the release engineer runs a script which exports the tree, expanding any keywords and updating the checksum file as necessary, and then the release engineer signs the checksum file! As has already been stated, if this doesn't work, you probably don't have a well defined and formal release process. Just because a developer has signed a checksum doesn't mean that the tree is suitable for release; that's the job of the release engineer to confirm, probably after running a set of regression test suites. And in fact, with git, it's pointless for the developer to sign a checksum file and then commit it, since git is already maintaining checksums as an integral part of how revisions are named.
Changing Gentoo release process won't make Git the best choice while other SCM candidates can provide the same functionalities that Gentoo needs without changing the process. -- Duy - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html