From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] rebasing security
Date: Tue, 12 Aug 2025 19:04:34 +0200 (CEST)
Message-ID: <d1e9da03-a621-513d-4288-efb0aafa2480@passwd.hu> (raw)
In-Reply-To: <CABPLASTsfShhVkZKU5rS9CTUhhZsxBFH9VidhgSXQ31MR4EG6Q@mail.gmail.com>
On Tue, 5 Aug 2025, Kacper Michajlow wrote:
> On Mon, 4 Aug 2025 at 23:38, Marton Balint <cus@passwd.hu> wrote:
>>
>>
>>
>>
>> - Previously it was pretty clear from git history who actually committed
>> a change from the comitter field. With using forgejo the comitter
>> field no longer shows the person who actually *committed* the change to
>> the main repo, but it is inherited from the original pull request commit
>> instead, so it simply shows the original author of the patch.
>
> I don't think this is accurate. Committer field is set to the person
> who clicks the "merge" button. Same as they would manually git push
> the patches.
Even if the merge is fast forward? Because there is a pull request I
merged via forgejo, and committer was not updated:
09828e7fe214a28cacfb805605bd5b19041d1f68
Regards,
Marton
_______________________________________________
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-08-12 17:06 UTC|newest]
Thread overview: 19+ 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
2025-08-05 22:18 ` Alexander Strasser via ffmpeg-devel
2025-08-12 17:04 ` Marton Balint [this message]
2025-08-12 17:26 ` Timo Rothenpieler
2025-08-05 22:37 ` Michael Niedermayer
2025-08-06 6:51 ` Alexander Strasser via ffmpeg-devel
2025-08-06 11:50 ` 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=d1e9da03-a621-513d-4288-efb0aafa2480@passwd.hu \
--to=cus@passwd.hu \
--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