[FFmpeg-devel] [PATCH v3 0/2] Improve HWDeviceContext logging

[softworkz .]

> -----Original Message-----
> From: ffmpegagent <ffmpegagent at gmail.com>
> Sent: Samstag, 19. April 2025 16:43
> To: ffmpeg-devel at ffmpeg.org
> Cc: softworkz <softworkz at hotmail.com>
> Subject: [PATCH v3 0/2] Improve HWDeviceContext logging
> 
> This changeset
> 
>  * adds an av class category for hw device contexts
>  * assigns a color to it
>  * adds an item_name function to the av class for hw device context
> 
> 
> Before
> ======
> 
> [AVHWDeviceContext @ 00000260A9C63E00] Selecting d3d11va adapter 2
> [AVHWDeviceContext @ 00000260A9C63E00] Using device 8086:4c8a
> (Intel(R) UH..
> [AVHWDeviceContext @ 00000260A9BFFC40] Use Intel(R) Media SDK to
> create MF..
> [AVHWDeviceContext @ 00000260A9BFFC40] Initialize MFX session:
> implementat..
> [h264 @ 00000260AC0DC640] Reinit context to 1920x800, pix_fmt: yuv420p
> 
> 
> After
> =====
> 
> [D3D11VA @ 00000184942C25C0] Selecting d3d11va adapter 2
> [D3D11VA @ 00000184942C25C0] Using device 8086:4c8a (Intel(R) UHD
> Graphics..
> [QSV @ 00000184942601C0] Use Intel(R) Media SDK to create MFX session,
> API..
> [QSV @ 00000184942601C0] Initialize MFX session: implementation
> version is..
> [h264 @ 00000184964BA9C0] Reinit context to 1920x800, pix_fmt: yuv420p
> 
> (..unable to show the terminal color change in plain text e-mail)
> 
> 
> V2
> ==
> 
>  * Resolved merge conflicts
>  * PING
> 
> 
> V3
> ==
> 
> TWO QUESTIONS BEFORE PUSHING:
> 
>  1. Adding an enum member without affecting the value of the last
> member
>     (_NB)
> 
> =>Is that a MINOR or a MICRO version bump?
> 
>  2. The date in doc/APIchanges
> 
> => Should I adjust it to the date when pushing or keep the date it had
> in
> the submitted patchset?
> 


From the history of APIChanges, most of the time - but not always - the
date appears to be set to the date when it's finally pushed, so I'll 
go with that.


Could somebody please confirm the kind of version bump needed for this 
specific case?

Thanks
sw