From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: oliver@monzo.com Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 288b7ec2 for ; Fri, 16 Jun 2017 00:52:36 +0000 (UTC) Received: from eu-smtp-delivery-111.mimecast.com (eu-smtp-delivery-111.mimecast.com [207.82.80.111]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 983d76c2 for ; Fri, 16 Jun 2017 00:52:36 +0000 (UTC) Received: by mail-wr0-f199.google.com with SMTP id g46so5574996wrd.3 for ; Thu, 15 Jun 2017 18:07:38 -0700 (PDT) MIME-Version: 1.0 From: Oliver Beattie Date: Thu, 15 Jun 2017 18:07:17 -0700 Message-ID: Subject: Git tags To: wireguard@lists.zx2c4.com Content-Type: text/plain; charset=UTF-8 List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, I have noticed that when a new snapshot is released, it is tagged in the Git repository, and an old tag is typically removed. While I understand Wireguard is considered experimental, this is quite frustrating as a user of the project. Given tags in Git are extremely lightweight, would it be unreasonable to keep them around? Cheers, Oliver