[Development] Please warn of force pushes...
Qi Liang
Liang.Qi at digia.com
Tue May 14 07:48:57 CEST 2013
+1 for this.
I met with this non-fast-forward case today. Sometimes, when people are mirroring a git repo, and "git push --mirror" doesn't work well for some reason. Then "git push --all" is a second choice, and this non-fast-forward will break "git push --all". Better to warn of those force pushes. And even better to not do it in the main repo, like qt, qt5/*.
And these kinds of big feature branch, if needs to have non-fast-forward push, maybe better to happen in a clone repo. It's very easy to do before the gerrit ages.
Regards,
Liang
________________________________________
From: development-bounces+liang.qi=digia.com at qt-project.org [development-bounces+liang.qi=digia.com at qt-project.org] on behalf of Thiago Macieira [thiago.macieira at intel.com]
Sent: Monday, April 22, 2013 3:14 AM
To: development at qt-project.org
Subject: [Development] Please warn of force pushes...
My server just let me know:
>From git://gitorious.org/qt/qtbase
60fbb00..c5a3cfa dev -> dev
1f3a67e..f78842a stable -> stable
! [rejected] winrt -> winrt (non-fast-forward)
PLEASE let the mailing list know every time a history rewrite is about to
happen and when it has happened in one of the main repositories.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
More information about the Development
mailing list