Re:Y U NO commit??
by gmantastic on Monday October 20, 2014 @04:25PM
(#8484296)
> What do you think would be a good set of criteria for what should count as a meaningful unit of work?
I'd consider a meaningful unit of work to be a bug fixed, or feature implemented, at least to the extent that you have a runnable version of the code again (even if you intend to do further work to implement it better e.g. replacing hard-coding). I'd consider changes short of this as not worth commiting, as this would not be a good starting point for further work (I know it's cheap to branch with Git etc., but it just feels untidy to leave something so part-done).
Re:Y U NO commit??
by gmantastic on Monday October 20, 2014 @04:34PM
(#8484339)
Is the motivation for commit-on-write to get a kind of persistent history for undo/redo? That is an interesting idea.
> I think commiting should be done for a more meaningful unit of work than a single edit, something logically 'complete' akin to a transaction.
What do you think would be a good set of criteria for what should count as a meaningful unit of work?