From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kieran Kunhya <kieran618@googlemail.com>,
softworkz <softworkz@hotmail.com>
Subject: Re: [FFmpeg-devel] [PATCH 0/4] [Please Ignore] ci_test
Date: Wed, 7 May 2025 15:16:28 +0100
Message-ID: <CABGuwEmJMioc5OwH_ip5fQzAEoJzBksx=tSTY66WkTVCjBMN0w@mail.gmail.com> (raw)
In-Reply-To: <pull.75.ffstaging.FFmpeg.1746588271.ffmpegagent@gmail.com>
On Wed, May 7, 2025 at 4:24 AM ffmpegagent <ffmpegagent@gmail.com> wrote:
>
> This is for testing Patchwork CI builds, not for merging.
>
> softworkz (4):
> ci_test: Fail configure
> ci_test: Fail build
> ci_test: Fail fate
> ci_test: All good
>
>
>
> base-commit: 2b6303762fc0850b3bd841ebd234c336271f657c
> Published-As: https://github.com/ffstaging/FFmpeg/releases/tag/pr-ffstaging-75%2Fsoftworkz%2Fsubmit_ci_test-v1
> Fetch-It-Via: git fetch https://github.com/ffstaging/FFmpeg pr-ffstaging-75/softworkz/submit_ci_test-v1
> Pull-Request: https://github.com/ffstaging/FFmpeg/pull/75
Do you intend to regularly spam the mailing list (which is already
heavily cluttered and disorganised) with your CI?
Kieran
_______________________________________________
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".
next prev parent reply other threads:[~2025-05-07 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 3:24 ffmpegagent
2025-05-07 3:24 ` [FFmpeg-devel] [PATCH 1/4] ci_test: Fail configure softworkz
2025-05-07 3:24 ` [FFmpeg-devel] [PATCH 2/4] ci_test: Fail build softworkz
2025-05-07 3:24 ` [FFmpeg-devel] [PATCH 3/4] ci_test: Fail fate softworkz
2025-05-07 3:24 ` [FFmpeg-devel] [PATCH 4/4] ci_test: All good softworkz
2025-05-07 14:16 ` Kieran Kunhya via ffmpeg-devel [this message]
2025-05-07 17:06 ` [FFmpeg-devel] [PATCH 0/4] [Please Ignore] ci_test softworkz .
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='CABGuwEmJMioc5OwH_ip5fQzAEoJzBksx=tSTY66WkTVCjBMN0w@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=kieran618@googlemail.com \
--cc=softworkz@hotmail.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
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