all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Tue, 16 May 2023 14:02:16 +0200	[thread overview]
Message-ID: <87zg641o3b.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87jzx8egfx.fsf@cbaines.net> (Christopher Baines's message of "Tue, 16 May 2023 10:57:24 +0100")

Hello,

Christopher Baines <mail@cbaines.net> writes:

> While I realise that waiting to make changes is fustrating, I think it's
> important to try and build things before merging so that the effects are
> known. This is also good motivation to get more hardware helping to
> build things to speed up the process.

I opened the issue because the "tex-team" branch was fully built on
CI, according to <https://ci.guix.gnu.org/eval/461653>.

Should I have looked elsewhere before asking for the merge?

Regards,
-- 
Nicolas Goaziou




  reply	other threads:[~2023-05-16 12:03 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 [this message]
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
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=87zg641o3b.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.