Steffen Prohaska <prohaska@xxxxxx> writes: > git push reports errors if a remote ref is not a strict subset > of a local ref. The push wouldn't be a fast-forward and is > therefore refused. This is in general a good idea. > This commit teaches git push to be quiet if the local is a strict > subset of the remote and no refspec is explicitly specified on > the command line. If the --verbose flag is used a "note:" is > printed for each ignored branch. What happens to the summary reporting after such a push? Does it say "branch foo was not pushed because you did not touch it since you fetched and it is already stale with respect to the remote side which has updates since then"? How does this interact with the "pretend we have fetched immediately after we pushed by updating the corresponding remote tracking branch" logic? - 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
