From: "Stefan Näwe" <stefan.naewe@atlas-elektronik•com>
To: Javier Domingo Cansino <javierdo1@gmail•com>,
Junio C Hamano <gitster@pobox•com>
Cc: "git@vger•kernel.org" <git@vger•kernel.org>,
Linux Kernel <linux-kernel@vger•kernel.org>
Subject: Re: [ANNOUNCE] Git v1.9-rc0
Date: Wed, 22 Jan 2014 16:49:22 +0100 [thread overview]
Message-ID: <52DFE882.2040605@atlas-elektronik.com> (raw)
In-Reply-To: <CALZVapmqcFjjKeURHdP4chkB+T2--caJZYiJBzdwq7Ou=HzO5w@mail.gmail.com>
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
??
(As long as Junio continues to push to github, of course)
Stefan
--
----------------------------------------------------------------
/dev/random says: Folks who think they know it all bug those of us who do
python -c "print '73746566616e2e6e616577654061746c61732d656c656b74726f6e696b2e636f6d'.decode('hex')"
next prev parent reply other threads:[~2014-01-22 15:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 21:03 What's cooking in git.git (Jan 2014, #03; Thu, 16) Junio C Hamano
2014-01-21 22:14 ` [ANNOUNCE] Git v1.9-rc0 Junio C Hamano
2014-01-22 12:53 ` Javier Domingo Cansino
2014-01-22 15:42 ` Junio C Hamano
2014-01-22 15:49 ` Stefan Näwe [this message]
2014-01-22 16:11 ` Junio C Hamano
2014-01-22 17:26 ` Vicent Martí
2014-01-22 18:10 ` Junio C Hamano
2014-01-22 20:30 ` Ken Moffat
2014-01-22 21:04 ` Junio C Hamano
2014-01-22 23:11 ` Ken Moffat
2014-01-23 2:09 ` Jeff King
2014-01-23 18:15 ` Junio C Hamano
2014-01-24 23:36 ` Jeff King
2014-01-27 22:56 ` Junio C Hamano
2014-01-28 0:04 ` Jeff King
2014-01-27 17:59 ` Kacper Kornet
2014-01-27 18:58 ` Jonathan Nieder
2014-01-28 12:28 ` Kacper Kornet
2014-01-30 22:20 ` Sitaram Chamarty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52DFE882.2040605@atlas-elektronik.com \
--to=stefan.naewe@atlas-elektronik$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=javierdo1@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox