Re: [Emacs-diffs] master b6610d5 2/4: emacs-lisp/package.el: Refactor pre-execute prompt

[Artur Malabarba]

> What I would do in this situation is work on a branch, make
> fine-grained commits there, and then merge them all onto master in a
> single merge-commit.  Then, if someone follows first-parent, they'd
> see a single commit with the feature, while still being able to
> discern the separate commits you made during development.

Thanks, I like that idea.

> No, it's a judgment call.  For me, an important question that helps
> the decision is "will I ever want to revert that single changeset?"
> YMMV, most probably.

Ok. The question I usually ask myself is “Is it conceivable this
changeset might intruduce a bug?”
This way tools like git bisect become considerably more useful (not
that I've ever had to use it for Emacs specifically).