From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Oliver Beattie <oliver@monzo.com>, wireguard@lists.zx2c4.com
Subject: Re: Git tags
Date: Thu, 15 Jun 2017 21:14:29 -0400 [thread overview]
Message-ID: <87a858n37u.fsf@fifthhorseman.net> (raw)
In-Reply-To: <CAA9f-OfbUrvM5PgL-ZHMCzDJuX9Vcoc84TJkK9yU7DGK7Tf2xw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
On Thu 2017-06-15 18:07:17 -0700, Oliver Beattie wrote:
> 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.
Huh, i hadn't noticed that older tags had been removed in the canonical
upstream git repo, i agree that's unusual and rather strange.
> Given tags in Git are extremely lightweight, would it be unreasonable
> to keep them around?
The repository where i record debian packaging changes includes a full
copy of the upstream repo (at least as far as what's been packaged) and
that naturally includes the older tags as well:
https://anonscm.debian.org/git/collab-maint/wireguard.git/refs/tags
You're always welcome to pull the tags from there (the upstream takgs
should all be cryptographically signed by Jason, so you can verify
authenticity even if the network source is different).
regards,
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-06-16 2:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 1:07 Oliver Beattie
2017-06-16 1:14 ` Daniel Kahn Gillmor [this message]
2017-06-16 2:44 ` Jason A. Donenfeld
2017-06-16 12:07 ` Martin Eskdale Moen
2017-06-16 12:08 ` Jason A. Donenfeld
2017-06-16 12:12 ` Martin Eskdale Moen
2017-06-16 12:23 ` Jason A. Donenfeld
2017-06-16 16:40 ` Oliver Beattie
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=87a858n37u.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=oliver@monzo.com \
--cc=wireguard@lists.zx2c4.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).