Thanks Terry for the clarifications: In terms of how to submit a patch for those two reviewed cases, or whatever, creating you own branch on launchpad and generating a merge request is probably the most convenient, for reviewers anyway.
That looks like what I was trying to suggest with too little understanding. In other projects, I was told that things had to be submitted formally (like bugs on launchpad) because otherwise it added to the workload of core developers. In any case, for whatever is proposed, it is Edward and core developers who dispose at their convenience, especially for optimizations. (And now I see that everything should have unit tests.) I'm also assuming separate branches on bzr keeps everything safe. (Caveat: the only thing I know about bzr and launchpad is that if type "bzr pull" at the command line in the proper folder, I get a shiny new Leo!). On Monday, 25 November 2013 09:46:06 UTC-8, Matt Wilkie wrote: > > > On Mon, Nov 25, 2013 at 7:31 AM, Reinhard Engel < > [email protected] <javascript:>> wrote: > >> And now I learned that is is not the place to discuss such code details. > > > I don't think that is the correct conclusion to draw from the > conversation. This is most definitely the place to discuss code and debate > the relative merits of proposed approaches and changes. > > -matt > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
