| commit | 1952aa1d5735ccbedd832620e43db3e03fc77088 | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Tue, 2 Oct 2007 16:52:22 +0000 (2 12:52 -0400) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Wed, 3 Oct 2007 04:21:50 +0000 (3 00:21 -0400) | ||
| tree | 66e919f794f04783a5a9154295b99dbdc0a02b52 | treesnapshot (tar.gz zip) |
| parent | e73bfa7709b108575e6ea73d6e97fc3efd967b38 | commitdiff |
git-gui: Allow forced push into remote repository
Some workflows allow the user to forcefully update a remote branch,
such as in a "proposed updates" (aka "pu") branch where the branch
is rewound and rebuilt on a daily basis against the current master
branch. In such a case the "--force" or leading + must be used to
make git-push execute anyway, even though it may be discarding one
or more commits on the remote side.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Some workflows allow the user to forcefully update a remote branch,
such as in a "proposed updates" (aka "pu") branch where the branch
is rewound and rebuilt on a daily basis against the current master
branch. In such a case the "--force" or leading + must be used to
make git-push execute anyway, even though it may be discarding one
or more commits on the remote side.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| lib/transport.tcl | diffblobblamehistory |