all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sharlatan Hellseher <sharlatanus@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 74138@debbugs.gnu.org, ashish.is@lostca.se
Subject: [bug#74138] [PATCH v1] gnu: yt-dlp: Update to 2024.10.22.
Date: Mon, 18 Nov 2024 09:50:37 +0000	[thread overview]
Message-ID: <CAO+9K5q3G6vzcEKepeuRCcoh+TYD237Wz9ixWULp3kVo6kjKkA@mail.gmail.com> (raw)
In-Reply-To: <87mshwgb9k.fsf_-_@gnu.org>

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

Hi,

I'll give it a try tonight.

Thanks,
Oleg

On Mon, 18 Nov 2024, 09:08 Ludovic Courtès, <ludo@gnu.org> wrote:

> Hey Sharlatan & Ashish,
>
> Looks like qa.guix is not processing much these days so perhaps if it
> works for you, you can go ahead and push.
>
> Ludo’.
>

[-- Attachment #2: Type: text/html, Size: 713 bytes --]

  reply	other threads:[~2024-11-18  9:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31 16:25 [bug#74138] [PATCH v1] gnu: yt-dlp: Update to 2024.10.22 Jakob Kirsch via Guix-patches via
2024-10-30 22:14 ` Doğan Çeçen
2024-11-01 21:41 ` [bug#74138] [PATCH v2 0/2] " Sharlatan Hellseher
2024-11-01 21:41   ` [bug#74138] [PATCH v2 1/2] gnu: python-websockets: Update to 13.0 Sharlatan Hellseher
2024-11-01 21:41   ` [bug#74138] [PATCH v2 2/2] gnu: yt-dlp: Update to 2024.10.22 Sharlatan Hellseher
2024-11-04  9:21     ` [bug#74138] [PATCH] gnu: yt-dlp: Update to 2024.11.04 ashish.is--- via Guix-patches via
2024-11-18  9:08       ` [bug#74138] [PATCH v1] gnu: yt-dlp: Update to 2024.10.22 Ludovic Courtès
2024-11-18  9:50         ` Sharlatan Hellseher [this message]
2024-11-18 17:47           ` Ashish SHUKLA via Guix-patches via
2024-11-18 17:46       ` [bug#74138] [PATCH] gnu: yt-dlp: Update to 2024.11.18 ashish.is--- via Guix-patches via
2024-11-18 23:35 ` bug#74138: [PATCH v1] gnu: yt-dlp: Update to 2024.10.22 Sharlatan Hellseher

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=CAO+9K5q3G6vzcEKepeuRCcoh+TYD237Wz9ixWULp3kVo6kjKkA@mail.gmail.com \
    --to=sharlatanus@gmail.com \
    --cc=74138@debbugs.gnu.org \
    --cc=ashish.is@lostca.se \
    --cc=ludo@gnu.org \
    /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.