On Sat, 13 Sep 2014 01:58:20 +0200, wm4 wrote: > On Fri, 12 Sep 2014 15:27:00 -0800 > Lou Logan <l...@lrcd.com> wrote: > > > Also slightly reorder mailing lists by "category" of development, user > > help, then logs. > > > > Also link some phrases to relevant pages. > > > > Signed-off-by: Lou Logan <l...@lrcd.com> > > --- > > src/contact | 25 ++++++++++++------------- > > 1 file changed, 12 insertions(+), 13 deletions(-) > > > > diff --git a/src/contact b/src/contact > > index 640ae58..2d0d09e 100644 > > --- a/src/contact > > +++ b/src/contact > > @@ -32,30 +32,29 @@ > > </div> > > <br> > > <div class="list-group"> > > + <a class="list-group-item" > > href="https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-devel/";> > > + <strong>ffmpeg-devel</strong><br> > > + For discussions involving development of FFmpeg. Patches for > > FFmpeg should be submitted > > + here. It is <strong>not</strong> for development of software > > that use the FFmpeg libraries > > + and <strong>not</strong> for <a href="bugreports.html">bug > > reports</a>. > > + </a> > > I think inexperienced/new people would still get confused by this: what > if they have found a bug, but also made a patch that fixes it? > > ffmpeg-devel says not to report bugs. TRAC says not to post patches.
How should it be worded to be less confusing? _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
