Johannes Schlüter wrote:
Actually the real question here is WHY create a fork on github at all? The copy
> you are working on LOCALLY is the fork that you are developing on? Much of
the
> stuff on github and the other DVCS server sites is redundant? You only need
to
> publish your local changes to other developers who are working with you not
to
> the whole world?
since i can publish an experimental feature, get it
reviewed/tested/improved before pushing it to the main tree.
Mind that "other developers who are working with you" is potentially
everybody on this list;-)
But that is the point ... if everybody has their own published 'experimental
feature' repos, syncing those bits we are playing with looks like a nightmare?
Surly the point of DVCS is we share via some central pot, and these experimental
branches exist there? Having to keep track of who's bits you are playing with is
the messy bit :( And it's that which has caused problems with other projects,
where 'extensions' have grown in secondary repos ... and become the official
extension. That is what I think people are just trying to flag up.
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
