Junio C Hamano gits...@pobox.com writes:
After I re-read the one, I found that override somewhat a strange
expression. There is nothing that overrides or to be overriden.
Right, I actually meant overwrite.
How about putting it like this?
I'm not sure push out refs other than the current
Matthieu Moy matthieu@grenoble-inp.fr writes:
Junio C Hamano gits...@pobox.com writes:
After I re-read the one, I found that override somewhat a strange
expression. There is nothing that overrides or to be overriden.
Right, I actually meant overwrite.
How about putting it like this?
Matthieu Moy matthieu@imag.fr writes:
The behavior of git push --force is rather clear when it updates only
one remote ref, but running it when pushing several branches can really
be dangerous. Warn the users a bit more and give them the alternative to
push only one branch.
On 13-06-17 01:52 PM, Matthieu Moy wrote:
The behavior of git push --force is rather clear when it updates only
one remote ref, but running it when pushing several branches can really
be dangerous. Warn the users a bit more and give them the alternative to
push only one branch.
Signed-off-by:
Marc Branchaud marcn...@xiplink.com writes:
On 13-06-17 01:52 PM, Matthieu Moy wrote:
The behavior of git push --force is rather clear when it updates only
one remote ref, but running it when pushing several branches can really
be dangerous. Warn the users a bit more and give them the
5 matches
Mail list logo
