Christian Couder <chriscool@xxxxxxxxxxxxx> writes: > The current "git bisect skip" syntax is "git bisect skip [<rev>...]" > so it's already possible to skip a range of revisions using > something like: > > $ git bisect skip $(git rev-list A..B) > > where A and B are the bounds of the range we want to skip. > > This patch teaches "git bisect skip" to accept: > > $ git bisect skip A..B > > as an abbreviation for the former command. Although I fully realize that the established semantics of A..B in git is bottom-exclusive, top-inclusive, and this suggestion breaks the UI uniformity by deviating from that convention, I have to wonder if it would be more useful if you let the bottom commit (A in your example) also be skipped. I would suspect that it would be more useful than the "replace" one, but that is a separate issue. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
