Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Jacob Lifshay <programmerjake@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] rebasing security
Date: Mon, 4 Aug 2025 21:05:34 -0700
Message-ID: <CAC2bXD4g_W3QZUUDdappm7ptFSixBd217u7DedN386Rg9-wGrg@mail.gmail.com> (raw)
In-Reply-To: <CABPLASTsfShhVkZKU5rS9CTUhhZsxBFH9VidhgSXQ31MR4EG6Q@mail.gmail.com>

On Mon, Aug 4, 2025 at 8:06 PM Kacper Michajlow <kasper93@gmail.com> wrote:
> Slightly related, I don't like how simple the web ui commit log of
> forgejo is, it doesn't show commiter at all. For me this information
> is as important as the author. I'm keeping notes on forgejo usage and
> will share it when the time comes, it has some annoying limitations
> compared to other forges.

It shows both the author and committer if you go to the page for a
particular commit:
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/157d3b007e93d39483bdc79278911f84b68b3c56

Jacob
_______________________________________________
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".

      parent reply	other threads:[~2025-08-05  4:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-03 15:31 Michael Niedermayer
2025-08-03 15:38 ` Timo Rothenpieler
2025-08-03 15:43   ` James Almer
2025-08-03 18:08   ` Michael Niedermayer
2025-08-03 19:02 ` Michael Niedermayer
2025-08-03 20:01   ` Timo Rothenpieler
2025-08-03 20:29     ` Michael Niedermayer
2025-08-03 20:34       ` Timo Rothenpieler
2025-08-04 20:15   ` Alexander Strasser via ffmpeg-devel
2025-08-04 21:36     ` Marton Balint
2025-08-05  3:06       ` Kacper Michajlow
2025-08-05  3:18         ` Kacper Michajlow
2025-08-05  4:05         ` Jacob Lifshay [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=CAC2bXD4g_W3QZUUDdappm7ptFSixBd217u7DedN386Rg9-wGrg@mail.gmail.com \
    --to=programmerjake@gmail.com \
    --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