Re: [Libquicktime-devel] why not migrate cvs to git ? and libquicktime on github

[Sérgio B. <se...@se...>]

OK , with acknowledgement of the mailing list nothing particular
private was write . 

On Fri, 2018-02-02 at 10:52 +0100, Burkhard Plaum wrote:
> Hi,
> 
> Am 01.02.2018 um 18:05 schrieb Sérgio Basto:
> > On Tue, 2018-01-23 at 10:29 +0100, Burkhard Plaum wrote:
> > > Am 23.01.2018 um 01:18 schrieb Sérgio Basto:
> > > 
> > > > 
> > > > yes , I need more permissions at least to add git ...
> > > 
> > > Ok you should be admin now.
> > 
> > 
> > Hello
> > 
> > I saw your commit today ...
> > 
> > I have done the migration to git , and all went well
> 
> Yea I saw that, thanks a lot.
> 
> > Currently libquicktime doesn't compile with ffmpeg 3.5 (not yet
> > released ) but compiles with ffmpeg 3.4.1
> > 
> > I made one branch if I got something to fix , I will commit there ,
> > but
> > may I merge to master ? do you want review it before ? etc
> 
> If you can make a patch, I can take a look at it.
> We never had different branches for libquicktime, because of slow
> development and
> few active developers, so I'd not be against using just the master
> branch exclusively.
> But if people feel more save using a development branch it's also ok.
> 
> In the past we always supported a wide range of versions via #ifdefs.
> But I think the ffmpeg
> APIs got more stable nowadays. There are certainly parts of the
> libquicktime code which
> would deserve some cleanups.
> 
> Also, please use libquicktime-devel for communication. It's a quiet
> list but
> normally people are listening. Maybe there are also opinions about
> which ffmpeg
> versions to support.

My maintain could be on autotools and fix warning or deprecated
functions ... , if and when I got some time , I  may commit in
code_maintain branch of libquicktime , to you review before merge to
master. 

Thanks
-- 
Sérgio M. B.