19.03.2016 23:38, Wols Lists wrote: > But for the OP, read these books, and learn to use branches. This is the > classic Git workflow - every little task should have its own git branch > on your developer machine. Switching between branches is almost > cost-free, and then when you're ready to submit your work you rebase to > the latest master, squash your branch into a single commit (if it's not > too big), and upload it for review and committing.
It is fine for independent pieces of work when pull requests are accepted quickly. But suppose that you finished one piece, pushed it, created a pull request and start a new work that require previous changes to work. When you finished this work too, push it and create a new pull request before first one was even looked at, you'll end up with mess. -- WBR, SD. ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
