all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: pkill9 <pkill9@runbox.com>
Cc: 46337@debbugs.gnu.org
Subject: [bug#46337] A patch to enable building proprietary codecs in qtwebengine
Date: Sat, 06 Feb 2021 11:10:16 +0100	[thread overview]
Message-ID: <87a6shy0af.fsf@nckx> (raw)
In-Reply-To: <20210206014748.5b281d65@runbox.com>

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

Pkill,

pkill9 写道:
> A patch to enable building proprietary codecs in qtwebengine

LGTM, but please send a proper (‘git format-patch’-format) patch 
that can be applied with ‘git am’ with a standardised commit 
message.  See ‘info (guix)Submitting Patches’ and the git log.

> +                       "--webengine-pepper-plugins=no"
> +		       "-webengine-proprietary-codecs")))))

The indentation's off here.  Guix Scheme code uses spaces 
everywhere.

Thanks!

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2021-02-06 10:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06  1:47 [bug#46337] A patch to enable building proprietary codecs in qtwebengine pkill9
2021-02-06 10:10 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2021-02-06 13:05   ` Tobias Geerinckx-Rice via Guix-patches via
2021-02-07 18:12 ` Leo Famulari
2021-02-08 15:40   ` pkill9
2021-02-08 16:36     ` Leo Famulari
2021-02-08 22:53       ` pkill9
2021-02-08 23:44         ` pkill9
2021-02-09 21:17           ` Leo Famulari
2021-05-30 17:54 ` [bug#46337] Attempt to fix the build Sergey Trofimov
2021-06-07 21:01   ` bug#46337: " Leo Famulari
2021-05-30 18:47 ` [bug#46337] Clarification for the previous patch Sergey Trofimov
2021-05-30 20:00 ` [bug#46337] Update Sergey Trofimov

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=87a6shy0af.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=46337@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --cc=pkill9@runbox.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 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.