But I'm glad I wasted 2+ hours of my night on commit and review with a
project that is still trying to get off the ground.
I have to be honest, this won't happen to much with me. Dealing with a
project like falconjx with A LOT of moving parts, I cannot work like
this.
Mike
Quoting Michael Schmalle <apa...@teotigraphix.com>:
Also,
He should revert commit 1451144 because he put a binary SWC in the
repo which is a no no, and well dam I would just like some input on
this refactoring stuff before it changes since this project is still
developing.
Commit and review could end up be a serious setback with this
project if it happens this way.
Mike
Quoting Michael Schmalle <apa...@teotigraphix.com>:
I want 1451312 reverted
"Another major refactoring, but..."
Right, WAY TO MAJOR. This was to much to change in one commit.
Mike
Quoting Justin Mclean <jus...@classsoftware.com>:
Hi,
I not been following the exact changes here, but any changes to
SVN can be reverted if need be and any committer can veto a check
in if they feel there's a valid reason for doing so. That's part
of the commit then review process we have.
Can you discuss the changes made on list and come up with a way to
solve this?
Thanks,
Justin
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
