On Sun, Jun 28, 2020 at 01:22:58PM +0100, Derek Buitenhuis wrote: > On 26/06/2020 14:49, Nicolas George wrote: > > Probably a good idea, but these explanation should probably go in > > doc/ffprobe.texi. > > Good point. Will add that during when I send v2. > > > And I do not maintain ffprobe. > > I have not seen Stefano active in a long time. Do you suggest I CC him on the > v2 patch? > > I always thought CCing people on patches was a bit rude, so I haven't.
iam not who that question was directed to but i think ffprobe needs a new maintainer as Stefano seems (as you mention) not active ATM. looking at ffprobe git history, it seemed both myself and marton had applied patches from people other than themselfs to ffprobe "recently" so they did some ffprobe maintaince work. if marton wants to maintain ffprobe, i think noone would mind otherwise if not and noone else wants to fill that spot, i guess ffprobe is "community maintained" ATM. marton ? Thanks [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Awnsering whenever a program halts or runs forever is On a turing machine, in general impossible (turings halting problem). On any real computer, always possible as a real computer has a finite number of states N, and will either halt in less than N cycles or never halt.
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
