Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [FATE PATCH] Properly list test errors when there are no failed tests
Date: Sat, 28 Jun 2025 11:39:17 +0300 (EEST)
Message-ID: <a3862932-299c-6d50-6f10-ea7678191a8f@martin.st> (raw)
In-Reply-To: <20250628015303.GN29660@pb2>

On Sat, 28 Jun 2025, Michael Niedermayer wrote:

>>> Its a few years since the last change to fateserver, i think we dont
>>> have a script to update the checkout on the server from a git push.
>>> Its a while, i dont remember exactly :)
>>> so you have to update that checkout after pushing possibly
>>
>> I don't think I have access to any such server,
>
> I think you do, i see a ssh-rsa key for martin@sphere for
> fate@fate.ffmpeg.org
>
>> but if it's ok with you can
>> I (try to) push this patch to the gitosis repo,
>
> yes, we use gitolite not gitosis though

Ok - I've pushed the patch to git@git.ffmpeg.org:fateserver.git now.

It's not obvious if the change is deployed in practice or not, until we 
have another case of breakage where compiling some test binaries fail - so 
we'll need someone to check.

// Martin

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

      reply	other threads:[~2025-06-28  8:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 10:57 Martin Storsjö
2025-06-18  1:50 ` Michael Niedermayer
2025-06-27 12:43   ` Martin Storsjö
2025-06-27 19:03     ` Kacper Michajlow
2025-06-27 19:06       ` Martin Storsjö
2025-06-28  1:53     ` Michael Niedermayer
2025-06-28  8:39       ` Martin Storsjö [this message]

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=a3862932-299c-6d50-6f10-ea7678191a8f@martin.st \
    --to=martin@martin.st \
    --cc=ffmpeg-devel@ffmpeg.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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git