unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Kaelyn <kaelyn.alexi@protonmail.com>
Cc: 49412@debbugs.gnu.org
Subject: [bug#49412] [PATCH core-updates] gnu: libdrm: Update to 2.4.107.
Date: Tue, 06 Jul 2021 10:24:47 +0200	[thread overview]
Message-ID: <b2412871363393e13715d0474c328cee078b189b.camel@telenet.be> (raw)
In-Reply-To: <5Pvsg9OZD8vKwdm4EQxqmpNKGC2KiZuZYe_EUcoTjyP7HJwIh_BR3K7AWrE0B4qvbzJE58sQivIwjMr0qXGzc0NI9dKsvFoiefvgl7qQNdA=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]

Kaelyn schreef op ma 05-07-2021 om 15:58 [+0000]:
> [...]
> I'm not familiar with the "--without-tests=" flag and mechanism, but would be happy
> to add a patch for it. I've only recently started using Guix and this is my first
> patch submission (it's a precursor patch from my attempt to update mesa to 21.1.x);
> should I email that patch to 49412@debbugs.gnu.org to make it part of the same issue?

If you mean the 'when tests?' patch, then I'd send it to 49412@debbugs.gnu.org
to keep the libdrm patches together (maybe as a v2 patch series).  If you mean
‘updating mesa to 21.1.1x’, then I'd send that patch to guix-patches@gnu.org,
as updating 'mesa' seems much more complicated than only updating 'libdrm'
(see reply by John Kehayias).

There is some documentation in the chapter ‘16 Contributing’ in the manual
on the process (more specifically, the section ‘16.6 Submitting Patches’)
but it doesn't have much advice on when to split patch series ...

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2021-07-06  8:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05  8:43 [bug#49412] [PATCH core-updates] gnu: libdrm: Update to 2.4.107 Kaelyn Takata via Guix-patches via
2021-07-05 15:15 ` Maxime Devos
2021-07-05 15:58   ` Kaelyn via Guix-patches via
2021-07-06  8:24     ` Maxime Devos [this message]
2021-07-05 21:58 ` John Kehayias via Guix-patches via
2021-07-08  3:02   ` John Kehayias via Guix-patches via
2021-07-08 15:43     ` John Kehayias via Guix-patches via
2021-07-13 16:57 ` [bug#49412] [PATCH v2] " Kaelyn Takata via Guix-patches via
2021-07-26 14:19   ` Thiago Jung Bauermann via Guix-patches via
2021-07-31 10:03   ` bug#49412: [PATCH core-updates] " Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b2412871363393e13715d0474c328cee078b189b.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=49412@debbugs.gnu.org \
    --cc=kaelyn.alexi@protonmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).