Re: [AD] Commit access for Allegro 4.4.X

[SiegeLord <siegelordex@xxxxxxxxx>]

I think historically there was a rough requirement of multiple, sizable 
contributions, which I don't feel you've met.

In terms of speeding up merges, I'd say just send pull requests via 
github. Doing it manually via patches is unnecessarily slow and involved 
as you've found out. As you've seen, we pretty much merge anything on 
the 4.4. branch >.>. Sending a bunch of patches via this method will 
hopefully be faster, and satisfy the informal requirement above.

-SL

On 08/07/2017 08:12 PM, Edgar Reynaldo wrote:
> Hey guys and gals,
>
> I hereby nominate myself for the official Allegro 4 maintainer. Nobody 
> else is gonna do it, and I'm not going anywhere anytime soon as long as 
> I've got wifi and my lappie I'm gonna keep pluggin away at my GUI and 
> Allegro.
>
> I'm just tired of having to ask someone else to commit patches for 
> Allegro 4 when I could just do it myself.
>
> If I ever had any major patches or anything that might break anything, I 
> will gladly run it by everyone here on AD.
>
> How many people are there left now with commit access to Allegro?
>
> Anyway, long story short I'm committed, I work well with others, and I 
> want to help keep Allegro 4 there for the people who need legacy code 
> and can 't port without great effort.
>
> I want to see if I can get Allegro 4.4.X to work with a recent version 
> of MSVC. I think it will probably be difficult because of the DirectDraw 
> legacy requirement that is no longer provided. Was there a minimalist 
> set of DX headers and libs for MSVC?
>
> Comments? Concerns? Thoughts?
>
> Marc D. aka Edgar Reynaldo