| Re: [cdt-dev] Why CDT should switch to Git |
|
Great feedback gang. Keep raising bugs on egit so we can make sure they get resolved. The other thing we need to consider is timing. We need to both be cautious about disrupting development as well as be firm on a date so we set ourselves a deadline.
To help, I’d like to put a stake in the ground. Here we go. CDT will move to git at the end of June 2011. That gives us six months to train in git and to close on workflows around how we do patches and such (i.e. don’t count on Gerrit), and of course, gives us incentive
to ensure the bugs we’re raising on egit are fixed in Indigo. I think that should be sufficient. I’m open to other opinions as always, but sooner or later, we’ll need to put our collective foot down and proceed with this
for the good of the community. Doug From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Andrew Gvozdev With support of pull, push, merge, rebase egit 0.10 is a great step forward and lets manage these git workflows. I wish CDT would move to git soon but that would be fairly steep learning curve for committers who are not using git daily.
If we are talking egit, that includes in addition to git complexity all these small workarounds/micro-workflows one have to develop for himself in egit like overcoming compare etc. With 0.10 one could *almost* work without command line. I still have to resort
to command line to recover or redo some things egit wouldn't do properly. That includes spontaneous "dirty markers" on Windows bug 307560, false merge conflicts like in
bug 331078, ssh key problems bug 326526. Add compare/synchronize problems James mentioned and that would be my sore spots list.
Looking forward for that to improve in egit 0.20 version. Andrew |