Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] [ffmpeg-web] branch master updated. a23b3fe Website release notes for 5.0
Date: Mon, 17 Jan 2022 16:14:19 +0100 (CET)
Message-ID: <Mtcab3b--3-2@lynne.ee> (raw)
In-Reply-To: <a2f30a42-4e1d-ce9b-2993-c4c4d1458a00@gyani.pro>

17 Jan 2022, 16:04 by ffmpeg@gyani.pro:

>
>
> On 2022-01-17 08:30 pm, ffmpeg-git@ffmpeg.org wrote:
>
>> The branch, master has been updated
>>  via  a23b3fe406dcabfbed5f5b31f3f07362173a10cb (commit)
>>  from  c362eec3ccd1ebe4dafc8500b70238d96aa4ba64 (commit)
>>
>>
>> - Log -----------------------------------------------------------------
>> commit a23b3fe406dcabfbed5f5b31f3f07362173a10cb
>> Author:     Lynne <dev@lynne.ee>
>> AuthorDate: Tue Jan 4 15:59:31 2022 +0100
>> Commit:     Lynne <dev@lynne.ee>
>> CommitDate: Fri Jan 14 22:10:59 2022 +0100
>>
>>  Website release notes for 5.0
>>
>> diff --git a/src/download b/src/download
>> index b723674..7d78dd0 100644
>> --- a/src/download
>> +++ b/src/download
>> @@ -304,6 +304,42 @@ gpg: Good signature from "FFmpeg release signing key &lt;ffmpeg-devel@ffmpeg.org
>>  and much faster bug fixes such as additional features and security patches.
>>  </p>
>>  +  <h3 id="release_5.0">FFmpeg 5.0 "Lorentz"</h3>
>> +
>> +  <p>
>> +    5.0 was released on 2022-01-NN. It is the latest stable FFmpeg release
>>
>
> "NN"
>
>> +    from the 5.0 release branch, which was cut from master on 2022-01-04.
>> +  </p>
>> +  <p>It includes the following library versions:
>> +  </p>
>> +  <pre>
>> +libavutil      57. 17.100
>> +libavcodec     59. 18.100
>> +libavformat    59. 16.100
>> +libavdevice    59.  4.100
>> +libavfilter     8. 24.100
>> +libswscale      6.  4.100
>> +libswresample   4.  3.100
>> +libpostproc    56.  3.100</pre>
>> +  <div class="row">
>> +    <div class="col-md-3">
>> +      <a class="btn btn-success" href="releases/ffmpeg-5.0.tar.xz">Download xz tarball</a>
>> +      <small><a href="releases/ffmpeg-5.0.tar.xz.asc">PGP signature</a></small>
>> +    </div> <!-- col -->
>> +    <div class="col-md-3">
>> +      <a class="btn btn-success" href="releases/ffmpeg-5.0.tar.bz2">Download bzip2 tarball</a>
>> +      <small><a href="releases/ffmpeg-5.0.tar.bz2.asc">PGP signature</a></small>
>> +    </div> <!-- col -->
>> +    <div class="col-md-3">
>> +      <a class="btn btn-success" href="releases/ffmpeg-5.0.tar.gz">Download gzip tarball</a>
>> +      <small><a href="releases/ffmpeg-5.0.tar.gz.asc">PGP signature</a></small>
>> +    </div> <!-- col -->
>> +    <div class="col-md-3 text-right">
>> +      <small><a href="https://git.ffmpeg.org/gitweb/ffmpeg.git/shortlog/n5.0">Changelog</a></small>
>> +      <a class="btn btn-success" href="https://git.ffmpeg.org/gitweb/ffmpeg.git/blob/refs/heads/release/5.0:/RELEASE_NOTES">Release Notes</a>
>> +    </div> <!-- col -->
>> +  </div> <!-- row -->
>> +
>>  <h3 id="release_4.4">FFmpeg 4.4.1 "Rao"</h3>
>>  <p>
>> diff --git a/src/index b/src/index
>> index 982fa33..62a514f 100644
>> --- a/src/index
>> +++ b/src/index
>> @@ -35,13 +35,73 @@
>>  News
>>  </h1>
>>  +  <h3 id="pr5.0">January Nth, 2022, FFmpeg 5.0 "Lorentz"</h3>
>>
>
> "Nth"
>

Thanks, fixed both placeholders.
The only date I did check was the split-off date, so I thought
I fixed all.
_______________________________________________
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:[~2022-01-17 15:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220117150005.CE9E668AFCF@ffbox0-bg.mplayerhq.hu>
2022-01-17 15:04 ` Gyan Doshi
2022-01-17 15:14   ` Lynne [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=Mtcab3b--3-2@lynne.ee \
    --to=dev@lynne.ee \
    --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