After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 642561 - Allow wip/* branches to have non-fast-forward pushes
Allow wip/* branches to have non-fast-forward pushes
Status: RESOLVED OBSOLETE
Product: sysadmin
Classification: Infrastructure
Component: Git
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Sysadmins
GNOME Sysadmins
Depends on:
Blocks:
 
 
Reported: 2011-02-17 12:04 UTC by Luca Bruno
Modified: 2013-11-21 14:56 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Luca Bruno 2011-02-17 12:04:53 UTC
Hello,
many times I personally rebase a wip branch against master, subsequently I have to push it and it's obviously a non fast-forward push. For this reason I have to delete the remote branch and push it again.

I'd like to request non-fast-forward pushes for wip/* branches.
Comment 1 Owen Taylor 2012-08-17 18:54:58 UTC
Done, but two caveats:
 
A) You need to provide the -f flag to push or git will still deny it
B) Mail will still be sent out about the commits - just as if you deleted the branch and pushed it again - if a commit has a new parent, it's a new commit according to GIT.

The only thing we could think of for B) is that for multi-commit pushes to WIP branches we *only* send out the "cover email" and don't send out the detailed email, and then we change the current logic:

 A) We send out detailed emails only for commits showing up for the first time in any branch in the repository

To:

 A) We send out detailed emails only for commits showing up for the first time in any non-WIP branch in the repository

So we always send out a detailed mail for any patch landing in a non-WIP branch. But people may want the normal detailed mails for patches landing in WIP branches, even if they land in large bunches?
Comment 2 Luca Bruno 2012-08-18 08:01:38 UTC
Thanks. I have no idea about other gnome modules, but for what concerns vala, wip branches are usually worked out by a single person and then deeply reviewed once they are complete. From this perspective I find it unnecessary to send detailed information.
Comment 3 Jasper St. Pierre (not reading bugmail) 2012-08-20 08:33:10 UTC
You could look at the subject of the patches and see if you can match them up. That might help a lot.
Comment 4 Andrea Veri 2013-11-21 14:56:44 UTC
The GNOME Infrastructure Team is currently migrating its bug / issue tracker away from Bugzilla to Request Tracker and therefore all the currently open bugs have been closed and marked as OBSOLETE.

The following move will also act as a cleanup for very old and ancient tickets that were still living on Bugzilla. If your issue still hasn't been fixed as of today please report it again on the relevant RT queue.

More details about the available queues you can report the bug against can be found at https://wiki.gnome.org/Sysadmin/RequestTracker.

Thanks for your patience,

the GNOME Infrastructure Team