On Wed, Aug 05, 2009 at 01:39:31PM -0700, Junio C Hamano wrote: > > When --quiet is given, the user generally only wants to see > > errors. > > That does not match what my cron job at day job expects. > > I'd welcome the warm and fuzzy feeling of seeing "ah, yes, we had changes > on those branches to push out last night". > > Maybe it is just me, but my gut feeling is that it would be more > appropriate to squelch only "already up to date" refs at least, at the > default level of quietness. I don't understand. Isn't that what "git push" _already_ does? Or are you saying you would like the "squelch progress" feature of 2/3, but not the "squelch ref status" of 3/3? In that case, are you not already doing something to squelch the progress? We could accomodate that by doubling --quiet to suppress ref status, though the transport interface seems to rely on flags (I guess we could have QUIET and REALLY_QUIET). -Peff -- 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