Hi, On Sun, 30 Sep 2007, Steffen Prohaska wrote: > > On Sep 30, 2007, at 12:25 AM, Junio C Hamano wrote: > > > Steffen Prohaska <prohaska@xxxxxx> writes: > > > > > - git push: prints updates of remote heads. A message about > > > failing to update a remote head may get lost. > > > > Please do not remove the report of successful update, as people often > > say "git push" or "git push $there" without explicitly saying which > > refs to push. When pushing out to publish, I say "git push ko" (to > > mean k.org) and I _want_ my positive feedback. > > Yes but it's pretty technical. > > A much simpler output could be easier to scan by a human > > updating 'refs/heads/master' .. fast forward .. ok. > updating 'refs/heads/pu' .. forced non-fast forward .. ok. > updating 'refs/heads/next' .. > ERROR: 'refs/heads/next' not updating to non-fast forward > exit(1) here. No, please no. This is way too short. If at all, please let 8c3275abcacb83ea3f4c4f4ceb2376799fc282bd be an example, and make git respect several different output levels, but not changing the default (at first). Ciao, Dscho - 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
