If it's just 2 lines, you can post them in the group or create an issue and let us know.
-- Ikai Lan Developer Programs Engineer, Google App Engine Blogger: http://googleappengine.blogspot.com Reddit: http://www.reddit.com/r/appengine Twitter: http://twitter.com/app_engine On Mon, Nov 22, 2010 at 4:26 PM, Vanni.T <[email protected]> wrote: > Hi Ikai, > > about your prerelease feedback request, generally speaking we need a more > direct way to suggest you SDK patches. > > According to http://code.google.com/p/googleappengine/ we have to "post > the code for the patch in the issue". > But nothing can help you evaluating soon those patches because they are > hidden among thousands of issues without patches. > If a submitter could add a 'patch' label to the issue maybe it would be > better. > > For example, I submitted two (minor) new bugs with patch/fix and obviously > they have still "new" status: > http://code.google.com/p/googleappengine/issues/detail?id=4055 > http://code.google.com/p/googleappengine/issues/detail?id=3919 > > What is the GAE team preferred and effective source code SDK feedback path? > I'm really glad to give my 2 (LOC) cents to the project, I am using it for > my own first business project and I like FOSS so much! > > Thank you, > Vanni > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
