| Preparing cvs->git Migration: Developer workflow [message #930595]
||Tue, 02 October 2012 13:13
| katie evans
Registered: July 2012
Location: brisbane queensland austr...
I am currently trying to convert a customer from CVS to git. Unfortunately I am sort of stuck at primarily one topic:
Currently, development makes a patch from every new feature or bugfix and they have a complete toolset in place to use these patchsets for application updates (development/patch target is a web framework written in a scripting language). For the sake of stability, I may not change the update workflows and CVS to git at the same time.
Unfortunately, I could not find a sane workflow yet in Eclipse/EGit for this sort of patching workflow, because it seems like you can only create patches in EGit from one commit to its predecessor.
That probably means a developer wont be able to commit anything until his current task hs been completely implemented. Then he would commit and create a patch. Clearly, especially in the git-spirit of "commit early, commit often" this is everything but optimal.
The other way I could think about would involve leaving Eclipse and making the patches outside in a command line environment. This also would be not good, because devs neither wont like the necessity to leave Eclipse nor would it be easy to train them for using git on the cmdline.
Since I am not an Eclipse guru, I wanted to ask you if you can imagine a way to find a proper workflow, preferably completely inside Eclipse, that would allow devs something like:
* create a local branch per task
* commit as often as they feel like
* create a patch that includes all changes made on that branch
* merge back the branch
How would you accomplish this?
Thank you very much for your help!
Powered by FUDForum
. Page generated in 0.02068 seconds