2008/6/25 Sam Vilain <sam@vilain.net>: > 'p4/perl' will have the inadvertant commit removed from it and track > perforce verbatim. > > 'blead' will get merged from blead every time I update it, and I'll > review and accept changes to files under Porting/ and any git > interoperability-related patches I receive and can be convinced are > safe. > > My intention with accepting these changes is that patches to Porting/ > would give instructions about how all of the maintenance operations that > worked under Perforce will work under git. In particular, there should > be a script which will use the output of 'git rev-list --cherry-pick', > as well as correlate information from the log messages, to say what > patches still need to be considered for application to the maintenance > branches. > > I'm hoping that this will stop there every being a fork while not > discouraging people who are willing to help the transition help out. > > If anyone has any objections, please raise them - I can of course just > put these under a different branch or something like that. > Thoughts/comments/flames? That sounds very sane to me.Thread Previous | Thread Next