Hi Andrew, 2014-10-01 12:06 GMT+02:00 Andrew Deryabin <[email protected]>: > 01.10.2014 08:52, Robert Jonsson пишет: > Hi, Robert! >> >> Hi Andrew, >> >> 2014-09-30 21:35 GMT+02:00 Florian Jung <[email protected]>: >>> >>> Am 30.09.2014 11:23, schrieb Andrew Deryabin: >>>> >>>> What about membership - It will be good (If all developers do not mind) >>>> - I can start a new branch (say lv2) where I'll make all lv2 development >>>> until it becomes ready for applying to master branch. >>> >>> Hey, welcome to the project :) >>> >>> yeah, a new branch sounds good. Looking forward to your stuff :) > > Ok, thank you :) >>> >>> >>>> Again, thanks for help :) I'll continue moving forward. >>> >>> I thank YOU for your efforts :) Let us know where we can help you >>> >>> Cheers, >>> flo >> >> Sounds good to me, a separate branch for the moment. I think I can fix >> access if I get your github alias? >> >> Also, Andrew, it seems I was a bit trigger happy, your mail with the >> patch did probably not make it to the developer mailinglist. I was >> cleaning stuff stuck from entering the mailinglist and I was a bit >> fast and deleted your mail :( it was stuck due to size restrictions. >> Seems it got through to the user-list though *shrug* > > Yes, I received email from list about message size, so I gzipped patch and > emailed it again :). Here is the link: > http://sourceforge.net/p/lmuse/mailman/message/32880933/
Ah, I see, then all is well. > > And today I've started own git server, so my commits will always be there > just in case. Public address is: > git://git.it-optima.ru/muse.git > default branch there is already lv2, so no need to checkout it, only clone > and build. > > My github account name is danvd > (I don't know what is githib alias :-[ = > > - can you tell me what is that?) I actually do not speak git or github that well ;), the account name was what I was after, I think. I invited you to muse, do check that it worked :) Regards, Robert ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
