Re: [FFmpeg-devel] Policy on ffmpeg-devel list and contributions [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-29 Thread Michael Niedermayer
On Wed, Nov 29, 2017 at 01:06:06PM -0800, Jim DeLaHunt wrote: > On 2017-11-29 06:53, Compn wrote: > > >[...] > >>Also, someone once observed that common sense is not very common. :-) > >sure, but please remember the DOCS are already quite verbose, and > >brevity is the soul of wit. so if you can s

Re: [FFmpeg-devel] Policy on ffmpeg-devel list and contributions [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-29 Thread Jim DeLaHunt
On 2017-11-29 06:53, Compn wrote: [...] Also, someone once observed that common sense is not very common. :-) sure, but please remember the DOCS are already quite verbose, and brevity is the soul of wit. so if you can say more with less verbiage that would be great. [...] Also please note that

Re: [FFmpeg-devel] Policy on ffmpeg-devel list and contributions [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-29 Thread Compn
On Mon, 27 Nov 2017 23:46:30 -0800, Jim DeLaHunt wrote: > On 2017-11-27 15:00, Carl Eugen Hoyos wrote: > > 2017-11-26 22:44 GMT+01:00 Jim DeLaHunt : > >> So, how realistic is this concern about non-subscribers sending > >> patches to > >> ffmpeg-devel? Does it actually happen? > > This is very

Re: [FFmpeg-devel] Policy on ffmpeg-devel list and contributions [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-27 Thread Jim DeLaHunt
On 2017-11-27 15:00, Carl Eugen Hoyos wrote: 2017-11-26 22:44 GMT+01:00 Jim DeLaHunt : So, how realistic is this concern about non-subscribers sending patches to ffmpeg-devel? Does it actually happen? This is very realistic afair. OK, and Lou Logan corroborates Carl Eugen: On 2017-11-27 15:1

Re: [FFmpeg-devel] Policy on ffmpeg-devel list and contributions [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-27 Thread Lou Logan
On Mon, Nov 27, 2017, at 02:22 PM, Lou Logan wrote: > > To clarify, in this case it was a reply, not a message. Should have typed "patch" there, not message. Actually reading message before sending this time. ___ ffmpeg-devel mailing list ffmpeg-devel@f

Re: [FFmpeg-devel] Policy on ffmpeg-devel list and contributions [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-27 Thread Lou Logan
On Mon, Nov 27, 2017, at 02:19 PM, Lou Logan wrote: > A very rough guess is that there are usually at least several > patches from unsubscribed users a week (in fact there was one in the > queue minutes ago). To clarify, in this case it was a reply, not a message. _

Re: [FFmpeg-devel] Policy on ffmpeg-devel list and contributions [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-27 Thread Lou Logan
On Mon, Nov 27, 2017, at 02:00 PM, Carl Eugen Hoyos wrote: > No, the mail admins could (or explain that I am wrong.) I would have to check each sender manually to see if they are in the membership database. It would be possible to do this, but not very practical. It would be easier for me to keep

Re: [FFmpeg-devel] Policy on ffmpeg-devel list and contributions [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-27 Thread Carl Eugen Hoyos
2017-11-26 22:44 GMT+01:00 Jim DeLaHunt : > On 2017-11-26 03:42, Carl Eugen Hoyos wrote: >> >> 2017-11-26 9:31 GMT+01:00 Jim DeLaHunt : >>> >>> -@subsection Documentation/Other >>> +@section Documentation/Other >>> +@subheading Subscribe to the ffmpeg-devel mailing list. >>> +It is important to be