> > > While the addition of a subcommand seems like a good idea, changing > default behaviour will no doubt break existing workflows. >
I agree on this point. However I have learned (where possible) to never rely on raw commands outputs in my wrappers. Indeed, I took over several years ago a Python script used to extract debug informations and the like from elf objects. This script relyed on outputs of 'nm' and 'readelf' commands. When we upgraded from Debian 6 to Debian 7, the outputs of those commands changed a bit and the script didn't work anymore. We then decided to rewrite the script in plain C using directly libdwarf and libelf. Someone wanting to get the list or current branch without relying on raw Fossil output could use "fossil json branch list" for that purpose. > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
