On Wed, Mar 04, 2009 at 11:04:52AM -0800, Shawn O. Pearce wrote: > Hmm. It would be nice to clean up these messages, but I > think the better way to do it is... > > > I think this would be improved somewhat with stderr processing to: > > > > remote: sh: bogus: command not found > > ... because then we can have positive proof that the remote said > something to the user, and we tagged it as being from the remote > side, just like we do with progress data in sideband, and then the > user can work from that information. Any local side errors are > very likely caused by the remote errors, so we shouldn't bother > displaying them. OK. I was hoping to avoid that because it's more work, but I think it is a better path in the long run. I'll add it to do my todo list. Unless you want to redeem yourself by working on it first. ;) -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
