On 21 September 2015 at 02:30, David Narvaez <[email protected]> wrote: > On Sun, Sep 20, 2015 at 7:57 PM, Jaroslaw Staniek <[email protected]> wrote: >> I see you're not used to the diverse term on github-alike sites: >> forking is more like creating a feature branch. The repo is separate >> but changes can be merged back (how it's a matter of tool set). > > It is just like feature branches, except every fly-by contributor will > have a clone repo with one patch and that way maintainers will have a > harder time figuring out what's been done where and who's working on > what. If this is the workflow you like, good for you, but I want to > opt-out from this madness and use git as it was meant to be used.
Thanks for your opinion but this is not the feature and case I was talking about. No fly-by contributor, no one-time patch that could indeed go via email (often private, untracked) as it happens now. If you seem to like things codified: violating code of conduct by using 'this madness', 'terrible idea' terms closes discussion with me for _you_ because you paint things in awful colors before actually understanding basics of the case. Feel free to meet on IRC to get idea what's the case about before continuing. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org Calligra Suite: : A graphic art and office suite - http://calligra.org Kexi: : A visual database apps builder - http://calligra.org/kexi Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek _______________________________________________ kde-community mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-community
