I simply has very little time. We moved to a new flat, wife's just about to give birth in a couple of weeks, work is at a stressful stage (first shareholders demo this week), and more. I hope to get to patches application as soon as I can. meanwhile other commiters are helping out.
On Thu, Aug 6, 2009 at 5:34 PM, Ola Herrdahl <herrd...@gmail.com> 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 > <johnsimons...@yahoo.com.au>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 <egoz...@gmail.com> 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 <herrd...@gmail.com> >> 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.comhttp://www.castleproject.orghttp://www.gotfriends.co.il >> >> > > > > -- Ken Egozi. http://www.kenegozi.com/blog http://www.delver.com http://www.musicglue.com http://www.castleproject.org http://www.gotfriends.co.il --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to castle-project-users@googlegroups.com To unsubscribe from this group, send email to castle-project-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
