From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id A8CCD1F424;
	Wed,  9 May 2018 20:29:38 +0000 (UTC)
Date: Wed, 9 May 2018 20:29:38 +0000
From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: tag v2 (pre-)release in git
Message-ID: <20180509202938.GA7755@dcvr>
References: <40c08aa2-3822-fc32-0aa1-f158607b0d5a@linuxfoundation.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <40c08aa2-3822-fc32-0aa1-f158607b0d5a@linuxfoundation.org>
List-Id: <meta.public-inbox.org>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> Would you be amenable to adding a v2-specific (pre-)release tag to the
> git repo? The only tag currently is v1.0.0, and, to make my life a bit
> easier, I wanted to get a ref to work from that's not just a sha1 jumble
> of characters. :)

Yup, just tagged v1.1.0-pre1.  I noticed the clone instructions for v2
repository still refer to "v1.1.0", so I'll make a "final" v1.1.0
at some point.  Thanks for the reminder.