-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A new version of this port was released upstream today [1]. I would like to update the pending new port [2] in a way that is considerate of ports users who may already be using this port based on the PR, potential committers who might adopt this PR, and freebsd-python@ subscribers who will have to wade through the reflected PR activity.
* "same/shar" Roll a fresh SHAR and post it to the existing PR. Simple for users and committers, but potentially annoying for list subscribers. * "same/diff" Generate a diff as if updating a committed port, but simply append it to [2]. A bit fiddly for users and committers, fairly easy on the list. * "new/shar" Request closure of [2], and proceed as if starting from scratch. PR churn, but makes life easy on users, committers, and listers. * "new/diff" Mainly here for completeness, but might be appealing to PR purists or overworked committers. Unless I receive persuasive guidance within a day or so, I will proceed with "same/diff". Thanks, John [1] http://pandas.pydata.org/#released-july-22-2012 [2] http://www.freebsd.org/cgi/query-pr.cgi?pr=169168 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQDIjrAAoJEEdKvTwaez9wuqAIAIsLDxvvU0nbGuOzwIJbnaEs SHIeNxsc8lazVZUMycIG+FZgZ5h4s9h9FSdorYK3x+2mHS7YDOV5YdJhlm1y5zYR QqnCVq4JbVksfJey1RIrw3u3HHDpqkwkRfig6V5L40E2K43XMmB2qVHPHaZ7nnZr OwhoJOu0I9UAGFulV282KWCj5ZdGKyx+DS59m7mBHMBtz7XJcjMT1UJuYc5G3zk9 E/43fdMl4Sn89hRSlLGTFmw2xmKRhKZ2GeW1Dzsl08qt9pcM+FLPJB3egOqLT4Wy P+1xss29fVQKbOkA5ZhScGJW/IF/jiKoilAorjKliB4blh+u2X6AHp3537932YU= =zk1k -----END PGP SIGNATURE----- _______________________________________________ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
