On Wed, Jan 22, 2014 at 5:11 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Stefan Näwe <stefan.naewe@xxxxxxxxxxxxxxxxxxxx> writes: > >> Am 22.01.2014 13:53, schrieb Javier Domingo Cansino: >>> Will there be any change on how tarballs are distributed, taking into >>> account that Google will be shutting down Google Code Downloads >>> section[1][2]? >>> >> >> Am I missing something or what's wrong with this: >> >> https://github.com/gitster/git/archive/v1.9-rc0.tar.gz >> >> or any >> >> https://github.com/gitster/git/archive/$TAG.tar.gz >> >> ?? > > Do these consume CPU every time somebody asks for a tarball? That > might be considered "wrong" depending on the view. No, our infrastructure caches frequently requested tarballs so they don't have to be regenerated on the fly. If you would prefer to distribute a different version of the tarball for the release (e.g. one with a different filename or folder structure), you can upload it directly to the release page of the tag: https://github.com/gitster/git/releases/tag/v1.9-rc0 We'll automatically mirror your release to S3 and serve it from there. You can also go ahead and edit the release page with the changelog you've posted in this email thread to make it more user friendly. WE WILL SERVE YOUR RELEASES, JUNIO BECAUSE WE LOVE YOU -vmg -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html