Hi Roch, I presume you're referring to Git's ability to send patches and only transfer file modifications. In fact, App Engine's deploy process already does this; whenever you deploy, only files that have never been seen before are uploaded. For instance, if you were to download a popular open-source app, modify the configuration file, and upload your app, likely only the configuration file and your app's configuration would be uploaded when you do this. App Engine doesn't upload diffs in the way git does, but this isn't practical given that App Engine can't rely on having other versions of the code to base a diff on.
-Nick Johnson On Thu, Nov 17, 2011 at 10:10 PM, Roch Delsalle <[email protected]> wrote: > Hi, > > I would like to know why Google App Engine isn't proposing an alternative > deploy workflow using Git. > That would save a lot of bandwidth. > > Roch > > -- > 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. > -- Nick Johnson, Developer Programs Engineer, App Engine -- 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.
