Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754452AbaA0W4g (ORCPT ); Mon, 27 Jan 2014 17:56:36 -0500 Received: from b-pb-sasl-quonix.pobox.com ([208.72.237.35]:47915 "EHLO smtp.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753722AbaA0W4e (ORCPT ); Mon, 27 Jan 2014 17:56:34 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=xAWgMtpBnnqFozUiwsWaO/8xTQUYlb9W iQrMvgvubCXPSZvz1+EwsMNpgmkEkKp9J+DKURqtiCylNqj9Qr5O90TGjfM4kjek frXOmkh4QXeuW8Uc1N/VZxNU7VguoBojUh12H2R/j8/WYYbKWa+3LPtZWiqwPMm5 72wBf5yXn3g= From: Junio C Hamano To: Jeff King Cc: Ken Moffat , Vicent =?utf-8?Q?Mart=C3=AD?= , Stefan =?utf-8?Q?N=C3=A4we?= , Javier Domingo Cansino , "git\@vger.kernel.org" , Linux Kernel Subject: Re: [ANNOUNCE] Git v1.9-rc0 References: <52DFE882.2040605@atlas-elektronik.com> <20140122203030.GB14211@milliways> <20140123020913.GF17254@sigill.intra.peff.net> <20140124233635.GA31371@sigill.intra.peff.net> Date: Mon, 27 Jan 2014 14:56:28 -0800 In-Reply-To: <20140124233635.GA31371@sigill.intra.peff.net> (Jeff King's message of "Fri, 24 Jan 2014 18:36:36 -0500") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Pobox-Relay-ID: 43C6EC3C-87A6-11E3-9200-1B26802839F8-77302942!b-pb-sasl-quonix.pobox.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Jeff King writes: > On Thu, Jan 23, 2014 at 10:15:33AM -0800, Junio C Hamano wrote: > >> Jeff King 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. > > I came up with the script below, which you can use like: > > ./script v1.8.2.3 git-1.8.2.3.tar.gz > > It expects the tag to already be pushed up to GitHub. I'll leave > sticking it on the "todo" branch and integrating it into RelUpload to > you. This can also be used to backfill the old releases (though I looked > on k.org and it seems to have only partial coverage). > > It sets the "prerelease" flag for -rc releases, but I did not otherwise > fill in any fields, including the summary and description. GitHub seems > to display reasonably if they are not set. Thanks. > -- >8 -- > #!/bin/sh > # > # usage: $0 > > repo=git/git > > # replace this with however you store your oauth token > # if you don't have one, make one here: > # https://github.com/settings/tokens/new > token() { > pass -n github.web.oauth Hmph, what is this "pass" thing? > } > > post() { > curl -H "Authorization: token $(token)" "$@" > } > > # usage: create > create() { > case "$1" in > *-rc*) > prerelease=true > ;; > *) > prerelease=false > ;; > esac > > post -d ' > { > "tag_name": "'"$1"'", > "prerelease": '"$prerelease"' > }' "https://api.github.com/repos/$repo/releases" > } > > # use: upload > upload() { > url="https://uploads.github.com/repos/$repo/releases/$1/assets" && > url="$url?name=$(basename $2)" && > post -H "Content-Type: $(file -b --mime-type "$2")" \ > --data-binary "@$2" \ > "$url" > } > > # This is a hack. If you don't mind a dependency on > # perl's JSON (or another parser), we can do a lot better. > extract_id() { > perl -lne '/"id":\s*(\d+)/ or next; print $1; exit 0' > } > > create "$1" >release.json && > id=$(extract_id upload "$id" "$2" >/dev/null && > rm -f release.json -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/