We need a Subversion training blog and a quiz for svn users before we give out commit rights. Also, are all committers on the dev mailing list? Are we certain that doing a reply to a commit is seen by the author? Can we have the post-commit mailer use the committer's username as the From field, so that if somebody does a Reply-All, they'll get two emails, assuming they are on the dev mailing list? Blair Ryan Schmidt wrote:
It would be better to use "svn cp" to copy the old port. By not doing this, the "svn log" of py25-gnupg gives misleading information: it claims the file just came into existence, created out of thin air, but in fact, it was based on another existing file. It would be better for the Subversion history to reflect that. "svn blame" would also be more useful as a result.
On Nov 13, 2007, at 16:28, source_changes@macosforge.org wrote:
Revision: 31016 http://trac.macosforge.org/projects/macports/changeset/31016 Author: ram@macports.org Date: 2007-11-13 14:28:24 -0800 (Tue, 13 Nov 2007)
Log Message: ----------- add py25-gnupg, copied from py-gnupg - closes #13010
Added Paths: ----------- trunk/dports/python/py25-gnupg/ trunk/dports/python/py25-gnupg/Portfile trunk/dports/python/py25-gnupg/files/ trunk/dports/python/py25-gnupg/files/patch-setup.py.diff
Added: trunk/dports/python/py25-gnupg/Portfile =================================================================== --- trunk/dports/python/py25-gnupg/Portfile (rev 0) +++ trunk/dports/python/py25-gnupg/Portfile 2007-11-13 22:28:24 UTC (rev 31016)
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev