Like Ken said, people are busy. I would drop an email here to get a commiter to have a look at it. I'll have a look MR-ISSUE-457 to see what needs to be done to get it in.
In regards to voting, I have raised that and added it to castle voice, please vote - http://castle.uservoice.com/pages/16605-official-castle-project-feedback-forum/suggestions/185412-enable-voting-for-patches-in-donjon Also you can vote this on up - http://castle.uservoice.com/pages/16605-official-castle-project-feedback-forum/suggestions/185410-review-monorail-patches-more-frequently Cheers John On Aug 7, 12:34 am, Ola Herrdahl <[email protected]> wrote: > Thanks Ken, I had missed the github mirror. > It solves my issues. > John, yes of course but now I was mainly looking for solution to how you > would maintain such a scenario until they are in trunk. > The rest of the patches are just me playing around, not sure I want to > bother you with that just yet. ;) > > But just out of curiosity why is MR-ISSUE-457 taking so long time? > And what does the process around patches look like? > E.g. without a voting feature in donjon how does a patch or feature find > it's way into trunk? > Are they picked on random or should I always drop an email here asking for > something to be reviewed? > > Regards, > > Ola > > On Thu, Aug 6, 2009 at 10:35 AM, John Simons > <[email protected]>wrote: > > > > > The other option is to ask us to review the patches and commit them > > into the trunk ;) Probably the preferred way. > > What other patches do you need committed? > > > And I myself would like MR-ISSUE-457 committed :) > > > Cheers > > John > > > On Aug 6, 6:31 pm, Ken Egozi <[email protected]> wrote: > > > one of the easiest options is to use the git based github mirror. > >http://github.com/leemhenson/castle/tree/master > > > > <http://github.com/leemhenson/castle/tree/master>the Master branch there > > is > > > kept in sync with Castle's trunk, and you can then fork and have your own > > > branch with your patches. > > > > On Thu, Aug 6, 2009 at 9:53 AM, Ola Herrdahl <[email protected]> wrote: > > > > Hi, > > > > > I have recently started using castle and have now run into a bit of a > > > > problem. > > > > (A general description of the problem is posted at stackoverflow ( > > > >http://stackoverflow.com/questions/1235188/how-to-maintain-a-locally-. > > .. > > > > )). > > > > > The issue I have is that I'm running against castle trunk but with a > > couple > > > > of patches (e.g. > > > >http://support.castleproject.org/projects/MR/issues/view/MR-ISSUE-457). > > > > And now I'm woundering how you would maintaining a patched copy of > > trunk? > > > > > Are there any official "experimental"-branches that alreay got most of > > the > > > > patches submitted? > > > > Or is this something every developer is maintaining locally? > > > > > Thanks, > > > > > Ola Herrdahl > > > > -- > > > Ken Egozi. > >http://www.kenegozi.com/bloghttp://www.delver.comhttp://www.musicglue... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
