From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] GitHub releases section is very old
Date: Sat, 29 Oct 2022 21:31:04 +0200
Message-ID: <20221029193104.GA1814017@pb2> (raw)
In-Reply-To: <ce2614e2-ffbb-b840-7bea-800c00357de1@rothenpieler.org>
[-- Attachment #1.1: Type: text/plain, Size: 1250 bytes --]
On Sat, Oct 29, 2022 at 02:53:34PM +0200, Timo Rothenpieler wrote:
> On 29.10.2022 14:36, * Neustradamus * wrote:
> > Hello all,
> >
> > It is possible to remove all releases from GitHub?
> > Because at right, we can see and it is not good promotion for this active project:
> > - https://github.com/FFmpeg/FFmpeg
> >
> > Releases 11
> > FFmpeg 3.0 Release
> > Latest on 15 Feb 2016
> > + 10 releases
> > - https://github.com/FFmpeg/FFmpeg/releases
> >
> > The important part is here:
> > - https://github.com/FFmpeg/FFmpeg/tags
> >
> > But it is possible to add all time in releases section, a new release with changelog...
>
> We should probably delete all existing releases instead, so they don't cause
> confusion like this.
> Github is just a mirror, not any kind of official release channel.
ill wait a few days so others can comment and then remove all releases from
github if thats the consensus at the time
i was not aware we had a old subset of releases listed there
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Its not that you shouldnt use gotos but rather that you should write
readable code and code with gotos often but not always is less readable
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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:[~2022-10-29 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 12:36 * Neustradamus *
2022-10-29 12:53 ` Timo Rothenpieler
2022-10-29 19:31 ` Michael Niedermayer [this message]
2022-11-26 21:14 ` Michael Niedermayer
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=20221029193104.GA1814017@pb2 \
--to=michael@niedermayer.cc \
--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