Dan Austin wrote: >> 3.1.1 team branches > >> For anyone with commit access, this is where large all new developments >> should go first. This includes any significant new features or invasive bug >> fixes that need extra testing. The changes should not move into release >> branches until they are reasonably tested and considered ready for release. > > Small grammar question/issue: > > ...large all new developments... > --or-- > ...all new large developments... > --or-- > ...large all-new developments... > > I know what it means, but it reads a little funny as is.
Yes, that is certainly weird. I'll re-word the sentence to say "all new large developments". Thanks, -- Russell Bryant Senior Software Engineer Open Source Team Lead Digium, Inc. _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
