"Philip Oakley" <philipoakley@xxxxxxx> writes: >> + Note that `--force` applies to all the refs that are pushed, >> + hence using `git push --all --force`, or `git push --force` >> + with `push.default` set to `matching` may override refs other >> + than the current branch (including local refs that are >> + strictly behind their remote counterpart). To force a push to >> + only one branch, use `git push <remote> +<branch>` instead of >> + `--force`. > > It would be useful to include a real example "e.g. `git push origin > +master`", or a link to specifying a refspec "see <refspec>... above", > such that the "+" doesn't get lost in the general text, as push is one > of the first few commands a new user is likely to be looking up (and > misunderstanding ;-), so let's make the + obvious Yes, why not. I'll point to the <refspec> section for detail, and just give an example here. > I did notice that the <refspec>... section doesn't actually associate > the "+" with the force action - Am I misunderstanding this? It says: By having the optional leading `+`, you can tell Git to update the <dst> ref even if it is not allowed by default (e.g., it is not a fast-forward.)" I think it's OK. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html