From: Mathieu Othacehe <m.othacehe@gmail.com>
To: Brice Waegeneire <brice@waegenei.re>
Cc: 40060@debbugs.gnu.org, me@tobias.gr, leo@famulari.name
Subject: [bug#40060] [PATCH v2 0/2] youtube-dl add ffmpeg and zsh-completion
Date: Mon, 23 Mar 2020 21:43:43 +0100 [thread overview]
Message-ID: <87lfnqssxs.fsf@gmail.com> (raw)
In-Reply-To: <1097e237aa50c0383d571c24f92702e7@waegenei.re>
> The first revision of this patch added pycryptodome as input, this version
> doesn't. BTW Tobias and Leo were against adding ffmpeg to youtube-dl.
Oops didn't see the small "v2". Well I'll revert this one until this is
clarified.
Sorry about that,
Mathieu
next prev parent reply other threads:[~2020-03-23 20:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 14:34 [bug#40060] [PATCH 0/2] youtube-dl add ffmpeg, pycryptodome and zsh-completion Brice Waegeneire
2020-03-14 14:42 ` [bug#40060] [PATCH 1/2] gnu: youtube-dl: Use ffmpeg and pycryptodome Brice Waegeneire
2020-03-14 17:21 ` Leo Famulari
2020-03-14 17:39 ` Brice Waegeneire
2020-03-14 17:47 ` Leo Famulari
2020-03-14 22:20 ` Tobias Geerinckx-Rice via Guix-patches via
2020-03-14 22:17 ` Tobias Geerinckx-Rice via Guix-patches via
2020-03-15 17:25 ` Leo Famulari
2020-03-17 9:06 ` Brice Waegeneire
2020-03-14 14:42 ` [bug#40060] [PATCH 2/2] gnu: youtube-dl: Add zsh completion Brice Waegeneire
2020-03-23 17:15 ` [bug#40060] [PATCH v2 0/2] youtube-dl add ffmpeg and zsh-completion Brice Waegeneire
2020-03-23 17:15 ` [bug#40060] [PATCH v2 1/2] gnu: youtube-dl: Add 'ffmpeg' as input Brice Waegeneire
2020-03-23 17:15 ` [bug#40060] [PATCH v2 2/2] gnu: youtube-dl: Add zsh completion Brice Waegeneire
2020-03-23 19:28 ` [bug#40060] [PATCH v2 0/2] youtube-dl add ffmpeg and zsh-completion Mathieu Othacehe
2020-03-23 20:23 ` Brice Waegeneire
2020-03-23 20:43 ` Mathieu Othacehe [this message]
2020-04-01 13:01 ` [bug#40060] [PATCH v3] gnu: youtube-dl: Add 'ffmpeg' as input Brice Waegeneire
2020-04-01 13:40 ` Tobias Geerinckx-Rice 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
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=87lfnqssxs.fsf@gmail.com \
--to=m.othacehe@gmail.com \
--cc=40060@debbugs.gnu.org \
--cc=brice@waegenei.re \
--cc=leo@famulari.name \
--cc=me@tobias.gr \
/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).