At Wed, 02 Feb 2011 09:30:28 -0800, Steven Watanabe wrote:
AMDG
On 2/2/2011 7:44 AM, Beman Dawes wrote:
To move discussion of Git beyond the arm waving stage, I'd like to suggest several concrete steps:
* Use the tag "[git]" to identify list postings discussing integration of Git into Boost daily life. If that gets unwieldy, we can start a separate mailing list.
* Start building documentation, with a lot of the initial effort going into rationale and "how to do it". To that end, I've started to populate a "Git" hierarchy on the Trac wiki: https://svn.boost.org/trac/boost/wiki/Git/GitHome. Please contribute!
The advantages look like a good start. I'd like to add:
Con: * The migration itself will cause a certain amount of disruption (transient) * Those who just don't care will have to learn a new tool (transient, subjective). * Links to svn will be broken. Trac and svn are currently heavily cross-linked. If someone has a way to avoid this problem, I'd be more than happy to withdraw it. (long-term).
John's modularization project maintains a complete correspondence of Git and SVN commits, so mapping those should be no problem.
(I'd just put this up, but I wanted to post here first to make sure that I'm not just missing something and that they're expressed in a fair way.)
Thank you, I think that's totally fair. -- Dave Abrahams BoostPro Computing http://www.boostpro.com