Re: What's cooking in git.git (Aug 2019, #04; Wed, 14)
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 16, 2019, 16:42 UTC
- Message-ID
- <xmqqlfvt12q0.fsf@gitster-ct.c.googlers.com>
- In-Reply-To
- <CAHd-oW4qo=aTrA90RmWsLeW44WKUiL2x9rzdToFRMq=ebKYksQ@mail.gmail.com>
Matheus Tavares Bernardino <matheus.bernardino@usp.br> writes:
Show 8 quoted lines
>> Thanks. Or we could just go the lazier route. A new stable release >> would happen within a day or two, and then in a week or so after that, >> the tip of 'next' gets rewound and rebuilt on top of it. We can >> discard the older copy and replace with the newer one when it happens. > > OK. I'm working on a v2 of mt/threaded-grep-in-object-store which > might depend on this patch. I can then send the newer version of this > patch as part of the series. Is that OK?
That would be good---just tell me what stale one I (may) still have in my tree that I need to discard when it happens. Thanks.