Re: [FFmpeg-devel] Accurately describing ffmpeg-cvslog list [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-28 Thread Clément Bœsch
On Mon, Nov 27, 2017 at 11:19:01PM +, Rostislav Pehlivanov wrote: > On 27 November 2017 at 23:05, Ronald S. Bultje wrote: > > > Hi, > > > > On Mon, Nov 27, 2017 at 6:03 PM, Carl Eugen Hoyos > > wrote: > > > > > 2017-11-26 22:57 GMT+01:00 Jim DeLaHunt : > > > > On 2017-11-26 03:42, Carl Eugen

Re: [FFmpeg-devel] Accurately describing ffmpeg-cvslog list [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-28 Thread Jim DeLaHunt
On 2017-11-27 15:03, Carl Eugen Hoyos wrote: 2017-11-26 22:57 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 : [...] + @subheading Subscribe to the ffmpeg-cvslog mailing list. -It is important to do this as the diffs of all com

Re: [FFmpeg-devel] Accurately describing ffmpeg-cvslog list [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-27 Thread Lou Logan
On Mon, Nov 27, 2017, at 03:20 PM, Mark Thompson wrote: > > If the intent is that -devel should always be used for replies, can you > set a reply-to header on -cvslog pointing to -devel? Done, thanks. Should have done that years ago. Didn't really think about the cvslog situation much until this d

Re: [FFmpeg-devel] Accurately describing ffmpeg-cvslog list [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-27 Thread Mark Thompson
On 28/11/17 00:12, Lou Logan wrote: > On Sun, Nov 26, 2017, at 12:57 PM, Jim DeLaHunt wrote: >> I'll observe that we have already heard other opinions: >> >> * Paul[2]: "Not at all. To be a contributor, it is not needed to >> subscribe to [ffmpeg-cvslog] list." >> * Timo[3]: "Usually if a d

Re: [FFmpeg-devel] Accurately describing ffmpeg-cvslog list [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-27 Thread Lou Logan
On Sun, Nov 26, 2017, at 12:57 PM, Jim DeLaHunt wrote: > I'll observe that we have already heard other opinions: > > * Paul[2]: "Not at all. To be a contributor, it is not needed to > subscribe to [ffmpeg-cvslog] list." > * Timo[3]: "Usually if a discussion comes up the mail from cvslog is

Re: [FFmpeg-devel] Accurately describing ffmpeg-cvslog list [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-27 Thread Rostislav Pehlivanov
On 27 November 2017 at 23:05, Ronald S. Bultje wrote: > Hi, > > On Mon, Nov 27, 2017 at 6:03 PM, Carl Eugen Hoyos > wrote: > > > 2017-11-26 22:57 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 : > > >> [...] > > >>>

Re: [FFmpeg-devel] Accurately describing ffmpeg-cvslog list [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-27 Thread Ronald S. Bultje
Hi, On Mon, Nov 27, 2017 at 6:03 PM, Carl Eugen Hoyos wrote: > 2017-11-26 22:57 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 : > >> [...] > >>> > >>> + > >>> @subheading Subscribe to the ffmpeg-cvslog mailing list. >

Re: [FFmpeg-devel] Accurately describing ffmpeg-cvslog list [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-27 Thread Carl Eugen Hoyos
2017-11-26 22:57 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 : >> [...] >>> >>> + >>> @subheading Subscribe to the ffmpeg-cvslog mailing list. >>> -It is important to do this as the diffs of all commits are sent there >>> and

[FFmpeg-devel] Accurately describing ffmpeg-cvslog list [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

2017-11-26 Thread Jim DeLaHunt
On 2017-11-26 03:42, Carl Eugen Hoyos wrote: 2017-11-26 9:31 GMT+01:00 Jim DeLaHunt : [...] + @subheading Subscribe to the ffmpeg-cvslog mailing list. -It is important to do this as the diffs of all commits are sent there and -reviewed by all the other developers. Bugs and possible improvemen