On Fri, Mar 20, 2015 at 12:56 PM, Abilio Marques <abili...@gmail.com> wrote:
> I personally would like a selective stash. Perhaps one where you can > selectively push some changes (then fossil could proceed to remove them > from the actual files), or selectively pop/apply some changes (but I > imagine this one could get things confusing, specially if used with apply). > ... > What are your opinions? Is this useful? Is this powerful? What would your > approaches be? > IMO it's inherently evil because it promotes checking in untested subsets. Automated tests require a full, valid tree. Checking in a part of a change may well lead to code which runs on your machine but doesn't run on remotes (continuous integration systems or other users). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "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
