[FFmpeg-devel] Forgejo questions

[FFmpeg-devel] Forgejo questions

[Michael Niedermayer]

[-- Attachment #1.1: Type: text/plain, Size: 1457 bytes --]

Hi all

how can i simply follow all changes, patches and discussions ?

prior to teh forgejo test, i simply go over all new mail in my ffmpeg-devel
folder.
In that folder,
    I can leave things as new that i want to look at later
    I can mark things as old that i have not read but dont plan to do anything with
    I can mark things as read that i have looked at and am done with (like after applying them locally)
    I can press a single button to apply the patch from a mail

Going over the whole list is not particularly difficult (the contents of
mails and patches may be difficult but the managing of mails/patches is not)

But with forgejo now there are mails in my inbox, in ffmpeg-devel neither
seem to contain patches, nor do they seem to represent dicussions with
correct threading. I dont even know from 3 mails which is a reply to which.

I see https://code.ffmpeg.org/FFmpeg/FFmpeg/activity
but that also seems not to really contain the level of detail that a simple
threaded mailinglist with new mails shows

Basically, can someone explain me how to use this effectively ?

I have figured out that with
fetch = +refs/pull/*/head:refs/remotes/fforge/pr/*
i can get all pull requests into my local git nicely

thx

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Those who are too smart to engage in politics are punished by being
governed by those who are dumber. -- Plato 

[-- 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".

Re: [FFmpeg-devel] Forgejo questions

[Timo Rothenpieler]

On 7/24/2025 7:30 PM, Michael Niedermayer wrote:
> Hi all
> 
> how can i simply follow all changes, patches and discussions ?
> 
> prior to teh forgejo test, i simply go over all new mail in my ffmpeg-devel
> folder.
> In that folder,
>      I can leave things as new that i want to look at later
>      I can mark things as old that i have not read but dont plan to do anything with
>      I can mark things as read that i have looked at and am done with (like after applying them locally)
>      I can press a single button to apply the patch from a mail

I have just made a sieve filter that puts all mails from Forgejo into 
their own folder, and I do have proper threads with all discussions (and 
pushes) in there.

Maybe some spam filter is somehow interfering, and eating some mails?

> Going over the whole list is not particularly difficult (the contents of
> mails and patches may be difficult but the managing of mails/patches is not)
> 
> But with forgejo now there are mails in my inbox, in ffmpeg-devel neither
> seem to contain patches, nor do they seem to represent dicussions with
> correct threading. I dont even know from 3 mails which is a reply to which.

The mails will never contain patches, they're just notifications.
They do contain a link to the patches and the PR number to fetch it via 
CLI though.

> I see https://code.ffmpeg.org/FFmpeg/FFmpeg/activity
> but that also seems not to really contain the level of detail that a simple
> threaded mailinglist with new mails shows
> 
> Basically, can someone explain me how to use this effectively ?

You should be able to use it exactly like you described, as long as you 
don't expect actual patches to be in the mails.
Everything else, comments, discussion, ... should be in an E-Mail to you.

> I have figured out that with
> fetch = +refs/pull/*/head:refs/remotes/fforge/pr/*
> i can get all pull requests into my local git nicely
> 
> thx
> 
> 
> _______________________________________________
> 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".

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

Re: [FFmpeg-devel] Forgejo questions

[Kyle Swanson]

Hi,

On Thu, Jul 24, 2025 at 10:46 AM Timo Rothenpieler
<timo@rothenpieler.org> wrote:
> The mails will never contain patches, they're just notifications.
> They do contain a link to the patches and the PR number to fetch it via
> CLI though.

If you append ".patch" or ".diff" to the url in the mail, you can get
the patch/diff directly. Github and Gitlab work in this way also.

e.g. https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20027.patch

Thanks,
Kyle
_______________________________________________
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".

Re: [FFmpeg-devel] Forgejo questions

[Timo Rothenpieler]

On 7/24/2025 7:58 PM, Kyle Swanson wrote:
> Hi,
> 
> On Thu, Jul 24, 2025 at 10:46 AM Timo Rothenpieler
> <timo@rothenpieler.org> wrote:
>> The mails will never contain patches, they're just notifications.
>> They do contain a link to the patches and the PR number to fetch it via
>> CLI though.
> 
> If you append ".patch" or ".diff" to the url in the mail, you can get
> the patch/diff directly. Github and Gitlab work in this way also.
> 
> e.g. https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20027.patch

Yeah, I usually even curl that and pipe it into git am when I'm in a rush.
Though a git alias that properly pulls the PR is also pretty simple.
_______________________________________________
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".

Re: [FFmpeg-devel] Forgejo questions

[Michael Niedermayer]

[-- Attachment #1.1: Type: text/plain, Size: 3112 bytes --]

Hi

On Thu, Jul 24, 2025 at 07:46:25PM +0200, Timo Rothenpieler wrote:
> On 7/24/2025 7:30 PM, Michael Niedermayer wrote:
> > Hi all
> > 
> > how can i simply follow all changes, patches and discussions ?
> > 
> > prior to teh forgejo test, i simply go over all new mail in my ffmpeg-devel
> > folder.
> > In that folder,
> >      I can leave things as new that i want to look at later
> >      I can mark things as old that i have not read but dont plan to do anything with
> >      I can mark things as read that i have looked at and am done with (like after applying them locally)
> >      I can press a single button to apply the patch from a mail
> 
> I have just made a sieve filter that puts all mails from Forgejo into their
> own folder, and I do have proper threads with all discussions (and pushes)
> in there.

Theres no threading
as in:

    (PR #123)
        Re:(PR #123)
        Re:(PR #123)
        Re:(PR #123)
        Re:(PR #123)
        Re:(PR #123)

what i expected is:

    (PR #123)
        Re:(PR #123)
            Re:(PR #123)
                Re:(PR #123)
        Re:(PR #123)
            Re:(PR #123)

So that one can see on first glance that there are 2 comments to the PR
and then following discussion on top of these 2 comments


> 
> Maybe some spam filter is somehow interfering, and eating some mails?
> 
> > Going over the whole list is not particularly difficult (the contents of
> > mails and patches may be difficult but the managing of mails/patches is not)
> > 
> > But with forgejo now there are mails in my inbox, in ffmpeg-devel neither
> > seem to contain patches, nor do they seem to represent dicussions with
> > correct threading. I dont even know from 3 mails which is a reply to which.
> 
> The mails will never contain patches, they're just notifications.
> They do contain a link to the patches and the PR number to fetch it via CLI
> though.

why dont the mails contain the patches ?
is there a disadvantage ?
Especially with simple like 1 line patches being able to just see it straight
could be nice


> 
> > I see https://code.ffmpeg.org/FFmpeg/FFmpeg/activity
> > but that also seems not to really contain the level of detail that a simple
> > threaded mailinglist with new mails shows
> > 
> > Basically, can someone explain me how to use this effectively ?
> 
> You should be able to use it exactly like you described, as long as you
> don't expect actual patches to be in the mails.
> Everything else, comments, discussion, ... should be in an E-Mail to you.

ive subscribed now with a 2nd account for watching only so i can filter the
watch all stuff away from things that i actively touched
otherwise watching the repo results in my inbox duplicating everything from
fffjo from ffmpeg-devel

Maybe we should collect all these suggestions on how to effectively use
forgejo in some place/file/wiki ?

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

No great genius has ever existed without some touch of madness. -- Aristotle

[-- 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".

Re: [FFmpeg-devel] Forgejo questions

[Kieran Kunhya via ffmpeg-devel]

>
> >
> > Maybe some spam filter is somehow interfering, and eating some mails?
> >
> > > Going over the whole list is not particularly difficult (the contents
> of
> > > mails and patches may be difficult but the managing of mails/patches
> is not)
> > >
> > > But with forgejo now there are mails in my inbox, in ffmpeg-devel
> neither
> > > seem to contain patches, nor do they seem to represent dicussions with
> > > correct threading. I dont even know from 3 mails which is a reply to
> which.
> >
> > The mails will never contain patches, they're just notifications.
> > They do contain a link to the patches and the PR number to fetch it via
> CLI
> > though.
>
> why dont the mails contain the patches ?
> is there a disadvantage ?
> Especially with simple like 1 line patches being able to just see it
> straight
> could be nice
>

Because you're meant to review patches inline on the web app.

Inline review, discussion and resolution on a web app is light years ahead
of email.

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

Re: [FFmpeg-devel] Forgejo questions

[Nicolas George]

Kieran Kunhya via ffmpeg-devel (HE12025-07-25):
> Inline review, discussion and resolution on a web app is light years ahead
> of email.

Nothing that happens in the monstrosity that is a web browser nowadays
can be said to be light years ahead of the tools we use, except if it is
in the direction of crashing into a black hole.

But you would not know it anyway, you are not using email, you are using
GMail. For development, GMail is to email what a Playskool Plastic Tool
Kit is to a real tool set.

You choose to use inferior tools, and then you want to force everybody
to use slightly-inferior tools so that you can use these inferior tools
a little less.

-- 
  Nicolas George
_______________________________________________
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".