Rebuttal: why not use tags to identify your major revisions and feature work? This way your bisect is rooted on feature releases or versions, rather than relyin

Rebuttal: why not use tags to identify your major revisions and feature work? This way your bisect is rooted on feature releases or versions, rather than relying on git log --since. It appears the time aspect is the primary argument presented, and I wouldn't consider using a workflow that didn't tag revisions, so I don't consider that an issue.