> > Both projects will still publish periodic U updates and numeric releases. The
> > combined sources also continues to have a GIT mirror at http://git.redump.net/mame
> ,
> > if you prefer that. You can still use the old methods of taking the source updates
> as
> > released and use those as a source base against your patches. Just expect delay or
> > rejection in your code submissions if the source tree has been modified too greatly
> > where your patches won't apply cleanly without modification.
> >
> > You make it sound like a public read-only SVN server of the MAME/MESS trees is the
> > worse thing to happen in the history of the project.. if it can bring you to
> > proclaiming you'll like never submit code again because of it.
>
> Agreed - really not understanding your point of view on this Howard, I have to assume
> there's some confusion or misconception on your part. Aside from the MESS merger,
> this is the same as it has been done behind the scenes 6 months ago, a year ago, even
> longer. If you weren't using it, then you were making your source patches against the
> U-releases - and that is still supported. It's just that: if you want to make your
> source patches against bleeding edge, and compile/test it with bleeding edge, now
> it's easier for you to do so.
>
> - Stiletto
Sorry guys but it's news to me. It's probably news to most occasional devs like myself as well. Go over to mamedev.org..... with the exception of the recent blog entry try to find a mention of a svn server anywhere....even in the developer docs. I've submitted changes/tweaks once in a blue moon for over 10 years now.
I'm not sure whre all the hate is coming from either... I'm just not fond of the SVN system.
|
Index 
Flat 
Re: Public read MAME/MESS merged SVN server
Reply
