On Sat, Aug 4, 2018 at 5:31 PM Martin Gagnon <eme...@gmail.com> wrote:
> Le sam. 4 août 2018 à 11:17, Stephan Beal <sgb...@googlemail.com> a > écrit : > >> If it was that common we would have realized the problem sooner ;). >> >> The problem with generating output for "no changes" is that we >> potentially break any automation which relies on an empty diff to mean "no >> changes". >> > > That is what stderr is for. > For this particular case i disagree. It's not an error condition and it seems (via a cursory glance) that fossil has so far used stderr only for logging and error cases. IMHO no output is the pedantically correct thing to do, but... i've got a long history of being in the minority when it comes to such opinions ;). Outputting "no differences" to stdout would (IMO) be fine if automation had the option to use --quiet to surprise that. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
