From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Christopher Baines <mail@cbaines.net>
Cc: 63521@debbugs.gnu.org
Subject: [bug#63521] Request for merging "tex-team" branch
Date: Fri, 02 Jun 2023 22:08:49 +0200 [thread overview]
Message-ID: <874jnpeiem.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <875y866vjq.fsf@cbaines.net> (Christopher Baines's message of "Fri, 02 Jun 2023 10:46:38 +0100")
Hello,
Christopher Baines <mail@cbaines.net> writes:
> So I still need to do this, however the more significant problem is that
> master has diverged significantly (in part at least due to the eudev
> change [1] not going to core-updates/another branch).
>
> 1: https://lists.gnu.org/archive/html/guix-devel/2023-05/msg00330.html
>
> I've got the qa-frontpage to flag this now, so there should be a warning
> at the top of [2] saying there's too many changes between the merge base
> and master.
>
> 2: https://qa.guix.gnu.org/branch/tex-team
>
> Would you be able to rebase the branch again?
I rebased the branch on top of 75bdd4b05253c0e6ca5399f60e424f0f00fdb673,
which is green.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2023-06-02 20:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 15:48 [bug#63521] Request for merging "tex-team" branch Nicolas Goaziou
2023-05-16 9:57 ` Christopher Baines
2023-05-16 12:02 ` Nicolas Goaziou
2023-05-16 12:05 ` Christopher Baines
2023-05-22 14:06 ` Ludovic Courtès
2023-05-22 14:36 ` Christopher Baines
2023-05-23 13:20 ` Christopher Baines
2023-05-24 14:36 ` Ludovic Courtès
2023-05-24 14:37 ` Ludovic Courtès
2023-05-24 17:28 ` Nicolas Goaziou
2023-05-25 9:13 ` Christopher Baines
2023-06-02 9:46 ` Christopher Baines
2023-06-02 20:08 ` Nicolas Goaziou [this message]
2023-06-11 9:31 ` Christopher Baines
2023-06-11 16:18 ` bug#63521: " Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jnpeiem.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=63521@debbugs.gnu.org \
--cc=mail@cbaines.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.