On Tue, Jun 26, 2018 at 2:37 AM, Eric Sunshine wrote:
> In addition to the t5702 failures, I'm also seeing failures of
> t0410.1, t5616.6 and t5616.7 at the tip of 'pu' as of [1], all of
> which seem to be related to these changes.
Yeah but only
On Mon, Jun 25, 2018 at 11:49 PM, Junio C Hamano wrote:
>
> Just an early warning, as I haven't even complained on patch titles
> of these patches in the series ;-)
>
> 5702.20 and 5702.21 seems to fail in standalone test, when these are
> directly queued on top of Git v2.18.0; I haven't looked
On Mon, Jun 25, 2018 at 5:49 PM Junio C Hamano wrote:
> Christian Couder writes:
> > This is a follow up from the patch series called "odb remote" [...]
>
> 5702.20 and 5702.21 seems to fail in standalone test, when these are
> directly queued on top of Git v2.18.0; I haven't looked into the
>
Christian Couder writes:
> This is a follow up from the patch series called "odb remote" that I
> ...
Just an early warning, as I haven't even complained on patch titles
of these patches in the series ;-)
5702.20 and 5702.21 seems to fail in standalone test, when these are
directly queued on
On Sat, Jun 23, 2018 at 2:18 PM, Christian Couder
wrote:
> High level overview of this patch series
>
>
> - Patch 1/9:
Sorry the patches are numbered X/11 but they should be numbered X/9 as
only the first 9 should be in the series and have been sent.
This is a follow up from the patch series called "odb remote" that I
sent earlier this year, which was itself a follow up from the patch
series called "Promisor remotes and external ODB support" that I sent
earlier this year, which was itself a follow up from previous series.
See the links section
6 matches
Mail list logo
