Please rebase any pending MRs and repush.
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.17 releases, and again with 6.18... It is
difficult to manage a regularly rebased tree
Please rebase any pending MRs and repush.
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.16 releases, and again with 6.17... It is
difficult to manage a regularly rebased tree
Please rebase any pending MRs and repush.
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.15 releases, and again with 6.16... It is
difficult to manage a regularly rebased tree
Please rebase any pending MRs and repush.
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.13 releases, and again with 6.14... It is
difficult to manage a regularly rebased tree
Please rebase any pending MRs and repush.
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.13 releases, and again with 6.14... It is
difficult to manage a regularly rebased tree
Please rebase any pending MRs and repush.
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.12 releases, and again with 6.13... It is
difficult to manage a regularly rebased tree
On Mon, Jul 15, 2024 at 03:16:14PM -0600, Justin Forbes wrote:
> Please rebase any pending MRs and repush.
>
> As we have done since 5.15, we have done this again for os-build, we expect
> to keep it up as a cadence with every upstream release. This means we
> will do it again when 6.11 releases,
Please rebase any pending MRs and repush.
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.11 releases, and again with 6.12... It is
difficult to manage a regularly rebased tree
Please rebase any pending MRs and repush.
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.10 releases, and again with 6.11... It is
difficult to manage a regularly rebased tree
Please rebase any pending MRs and repush.
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.8 releases, and again with 6.9... It is
difficult to manage a regularly rebased tree,
Please rebase any pending MRs and repush.
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.7 releases, and again with 6.8... It is
difficult to manage a regularly rebased tree,
Please rebase any pending MRs and repush.
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.6 releases, and again with 6.7... It is
difficult to manage a regularly rebased tree,
Please rebase any pending MRs and repush.
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.5 releases, and again with 6.6... It is
difficult to manage a regularly rebased tree,
Please rebase any pending MRs and repush.
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.4 releases, and again with 6.3... It is
difficult to manage a regularly rebased tree,
Please rebase any pending MRs and repush.
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.3 releases, and again with 6.4... It is
difficult to manage a regularly rebased tree,
Please rebase any pending MRs and repush.
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.2 releases, and again with 6.3... It is
difficult to manage a regularly rebased tree,
Please rebase any pending MRs and repush.
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.1 releases, and again with 6.2... It is
difficult to manage a regularly rebased tree,
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 6.0 releases, and again with 6.1... It is
difficult to manage a regularly rebased tree, because any outstanding
MR is invalidated a
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 5.19 releases, and again with 5.20... It is
difficult to manage a regularly rebased tree, because any outstanding
MR is invalidated
As we have done since 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 5.18 releases, and again with 5.19... It is
difficult to manage a regularly rebased tree, because any outstanding
MR is invalidated
As we did with 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 5.17 releases, and again with 5.18... It is
difficult to manage a regularly rebased tree, because any outstanding
MR is invalidated and ha
If you have a pending merge request, you will need to rebase your
source tree and force push so that things will cleanly merge.
As we did with 5.14, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 5.16 rele
If you have a pending merge request, you will need to rebase your
source tree and force push so that things will cleanly merge.
As we did with 5.13, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 5.15 rele
23 matches
Mail list logo
