Re: [PATCH v4 11/12] refs: implement logic to migrate between ref storage formats

> Jeff King <peff@peff.net> writes:
> 
> > In my fork I trigger Coverity runs based on my personal integration
> > branch, which is based on next plus a list of non-garbage topics I'm
> > working on. So I get to see (and fix) my own bugs before anybody else
> > does. But I don't see other people's bugs until they're in next.
> 
> I am on a mostly same boat but doing a bit better ;-) in that my
> daily driver is a point marked as 'jch', somewhere between 'next'
> and 'seen', that appears on "git log --first-parent --oneline
> master..seen", and this serves as a very small way [*] to see
> breakages by others before they hit 'next'.
> 
>     Side note: This does not work as well as I should, because my
>     use cases are too narrow to prevent all breakage from getting
>     into 'next'.