From: jgart via Guix-patches via <guix-patches@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 59372@debbugs.gnu.org, Tobias Geerinckx-Rice <me@tobias.gr>
Subject: [bug#59372] [PATCH] gnu: peek: Add missing input.
Date: Mon, 21 Nov 2022 13:38:04 -0600 [thread overview]
Message-ID: <20221121133804.GB16771@dismail.de> (raw)
In-Reply-To: <87mt8kut6x.fsf@gmail.com>
On Mon, 21 Nov 2022 18:13:26 +0100 zimoun <zimon.toutoune@gmail.com> wrote:
> Hi,
>
> Thanks for resuming #51202. :-)
>
> On Sat, 19 Nov 2022 at 03:50, Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org> wrote:
>
> > As far as I can tell, this change doesn't affect the peek
> > package's output at all. Am I mistaken? What should the
> > observable difference be, beyond ‘working’?
>
> Peek needs to be propagated. An issue is open,
I read through the open issue. Should I send a patch implementing lilyp's suggestion?
That's what I was also thinking of doing but I also had the question
regarding choosing between ffmpeg or gnome-shell. Should we prefer
ffmpeg? Would be cool if we could support choosing between ffmpeg or
gnome-shell.
Is there currently a way to do that?
next prev parent reply other threads:[~2022-11-21 19:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 1:27 [bug#59372] [PATCH] gnu: peek: Add missing input jgart via Guix-patches via
2022-11-19 2:50 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-19 4:07 ` jgart via Guix-patches via
2022-11-19 9:38 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-21 14:27 ` jgart via Guix-patches via
2022-11-21 15:14 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-21 20:18 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-21 20:58 ` jgart via Guix-patches via
2023-01-29 6:02 ` bug#59372: " 宋文武 via Guix-patches via
2022-11-21 17:13 ` [bug#59372] " zimoun
2022-11-21 19:38 ` jgart via Guix-patches via [this message]
2022-11-22 14:39 ` zimoun
2022-11-22 18:29 ` jgart via Guix-patches via
2022-11-19 9:13 ` ( via Guix-patches via
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=20221121133804.GB16771@dismail.de \
--to=guix-patches@gnu.org \
--cc=59372@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=me@tobias.gr \
--cc=zimon.toutoune@gmail.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.