On Wed, Sep 10, 2014 at 04:02:38PM -0700, Timothy Gu wrote: > On Wed, Sep 10, 2014 at 2:57 PM, Diego Biurrun <di...@biurrun.de> wrote: > > --- a/src/contact > > +++ b/src/contact > > @@ -4,7 +4,7 @@ > > > > <p> > > Please follow the netiquette when posting on Libav mailing lists, > > especially > > > -avoid <a href="http://en.wikipedia.org/wiki/Top-posting";>top-posting</a> > > and > > +avoid <a > > href="https://en.wikipedia.org/wiki/Posting_style#Top-posting";>top-posting</a> > > and > > Why? The original isn't dead.
No, but it redirects to the new link. Updating the link skips that intermediary step. > > --- a/src/news > > +++ b/src/news > > > @@ -800,9 +800,9 @@ conversion API in libavcodec. > > The <b>libpostproc</b> library now resides in a separate tree. It was fully > > independent of the other Libav libraries, not used by any of the tools, > > and saw very little development. For these reasons we have decided that it > > -has no place in Libav. A standalone Git tree is available > > -at <a href="http://git.videolan.org/?p=libpostproc.git";>VideoLAN</a> for > > -people wishing to use libpostproc. > > +has no place in Libav. A standalone Git tree is available at > > +<a > > href="https://git.videolan.org/?p=libpostproc.git;a=summary";>VideoLAN</a> > > +for people wishing to use libpostproc. > > </p> > > > > <p> > > @@ -1000,9 +1000,9 @@ conversion API in libavcodec. > > The <b>libpostproc</b> library now resides in a separate tree. It was fully > > independent of the other Libav libraries, not used by any of the tools > > and saw very little development. For these reasons we decided that it > > -has no place in Libav. A standalone Git tree is available > > -at <a href="http://git.videolan.org/?p=libpostproc.git";>VideoLAN</a> for > > -people wishing to use libpostproc. > > +has no place in Libav. A standalone Git tree is available at > > +<a > > href="https://git.videolan.org/?p=libpostproc.git;a=summary";>VideoLAN</a> > > +for people wishing to use libpostproc. > > </p> > > > > <p> > > Why? WTH? I could swear those links did not work earlier today ... > Is it possible for me to use part of this patch for the FFmpeg website? *sigh* - once more this feels like FFmpeg takes, takes, takes, and gives nothing in return (let's not even delve into the whole negativity thing). I don't particularly care, nor is any of this copyrightable anyway. Just do whatever you want with it. Diego _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
