From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Ken Moffat" <zarniwhoop@ntlworld.com>,
"Vicent Martí" <tanoku@gmail.com>,
"Stefan Näwe" <stefan.naewe@atlas-elektronik.com>,
"Javier Domingo Cansino" <javierdo1@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v1.9-rc0
Date: Thu, 23 Jan 2014 10:15:33 -0800 [thread overview]
Message-ID: <xmqqha8uva2i.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140123020913.GF17254@sigill.intra.peff.net> (Jeff King's message of "Wed, 22 Jan 2014 21:09:13 -0500")
Jeff King <peff@peff.net> writes:
> Junio, since you prepare such tarballs[1] anyway for kernel.org, it
> might be worth uploading them to the "Releases" page of git/git. I
> imagine there is a programmatic way to do so via GitHub's API, but I
> don't know offhand. I can look into it if you are interested.
I already have a script that takes the three tarballs and uploads
them to two places, so adding GitHub as the third destination should
be a natural and welcome way to automate it.
next prev parent reply other threads:[~2014-01-23 18:16 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
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 [this message]
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=xmqqha8uva2i.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=javierdo1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peff@peff.net \
--cc=stefan.naewe@atlas-elektronik.com \
--cc=tanoku@gmail.com \
--cc=zarniwhoop@ntlworld.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.