Re: [ANNOUNCE] git-test: run automated tests against a range of Git commits

2017-01-11 Thread Michael Haggerty
On 01/10/2017 10:35 AM, Jeff King wrote: > On Sun, Jan 08, 2017 at 10:52:25AM +0100, Michael Haggerty wrote: >> [...] Since my last email, I have implemented a bunch of what we discussed [1]. Because of the new semantics, I also *renamed the main command* from git test range [...] to

Re: [ANNOUNCE] git-test: run automated tests against a range of Git commits

2017-01-10 Thread Jeff King
On Sun, Jan 08, 2017 at 10:52:25AM +0100, Michael Haggerty wrote: > > I see the symmetry and simplicity in allowing the user to specify a full > > range. But it also seems like it's easy to make a mistake that's going > > to want to test a lot of commits. I wonder if it should complain when > >

Re: [ANNOUNCE] git-test: run automated tests against a range of Git commits

2017-01-08 Thread Michael Haggerty
On 01/07/2017 08:18 AM, Jeff King wrote: > On Fri, Jan 06, 2017 at 04:52:16PM +0100, Michael Haggerty wrote: > >> I just released `git test`, a script for running automated >> tests across a range of Git commits and keeping track of the results in >> git notes: >> >>

Re: [ANNOUNCE] git-test: run automated tests against a range of Git commits

2017-01-06 Thread Jeff King
On Fri, Jan 06, 2017 at 04:52:16PM +0100, Michael Haggerty wrote: > I just released `git test`, a script for running automated > tests across a range of Git commits and keeping track of the results in > git notes: > > https://github.com/mhagger/git-test > > This is a script that

[ANNOUNCE] git-test: run automated tests against a range of Git commits

2017-01-06 Thread Michael Haggerty
I just released `git test`, a script for running automated tests across a range of Git commits and keeping track of the results in git notes: https://github.com/mhagger/git-test This is a script that I've been using in one form or another for years and I find it really handy [1].