From: Martin Eskdale Moen <martinmoen@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Oliver Beattie <oliver@monzo.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Git tags
Date: Fri, 16 Jun 2017 12:07:18 +0000 [thread overview]
Message-ID: <CAKiCHuO49TvS-dhjtd7m8V_SOzPYMjTkBAM3KSyhWruLUYTPkg@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9oB5j3u20ePPouhOydb-GehgY6JRsE+mNs+CSs=KDb=tQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
Hi Jason
I usually find it useful when I'm provisioning with ansible to be able to
point to a tag and upgrade when I'm ready, so when I provision new nodes
they all have the same version, even if a new version is out.
On Fri, 16 Jun 2017 at 03:44 Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> Hi Oliver,
>
> On Fri, Jun 16, 2017 at 3:07 AM, Oliver Beattie <oliver@monzo.com> wrote:
> > Given tags in Git are extremely lightweight, would it be unreasonable
> > to keep them around?
>
> I can keep them around, no problem. I just thought they looked sort of
> cluttered, so I removed them, but if it's useful to you, I don't mind
> keeping them.
>
> What use case did you have in mind, anyway, for old tags?
>
> Jason
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
[-- Attachment #2: Type: text/html, Size: 1436 bytes --]
next prev parent reply other threads:[~2017-06-16 11:52 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
2017-06-16 2:44 ` Jason A. Donenfeld
2017-06-16 12:07 ` Martin Eskdale Moen [this message]
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=CAKiCHuO49TvS-dhjtd7m8V_SOzPYMjTkBAM3KSyhWruLUYTPkg@mail.gmail.com \
--to=martinmoen@gmail.com \
--cc=Jason@zx2c4.com \
--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).