Why is there a need for anything beyond "git commit" or "git push" or "git pull" to do anything? Why should I, as a developer, be required to micromanage the revision control mechanism? That's the fundamental point of my previous message. If I have to spend more time getting a commit through to the canonical repo than I do making a change to the code, that suggests to me whatever tool I'm using for revision control is not fit for purpose. If dealing with the common case, of someone committing before you, cannot be automated cleanly by git out of the box, how is it a better tool than the likes of svn?

On Wed, Feb 15, 2017 at 10:46 AM, Magnus Johnsson <magnusjjj@gmail.com> wrote:

Zachary, that is some seriously valuable input :). I was going to write a longer answer, with super simple answers, but I found that the super simple solutions to these are all the top results on google, stackoverflow. Seems like the situation has cleared up to be a *lot* simpler these days, like 2 to 3 commands copy paste, with helpfull comments on the what and why's :). Check it out?

_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev