[Bug 642561] Allow wip/* branches to have non-fast-forward pushes
- From: "sysadmin" (bugzilla.gnome.org) <bugzilla gnome org>
- To: gnome-infrastructure gnome org
- Subject: [Bug 642561] Allow wip/* branches to have non-fast-forward pushes
- Date: Fri, 17 Aug 2012 18:55:00 +0000 (UTC)
https://bugzilla.gnome.org/show_bug.cgi?id=642561
sysadmin | Git | unspecified
Owen Taylor <otaylor> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |otaylor redhat com
--- Comment #1 from Owen Taylor <otaylor redhat com> 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?
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the QA contact of the bug.
You are watching the assignee of the bug.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]