Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Oliver Beattie <oliver@monzo.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Git tags
Date: Fri, 16 Jun 2017 09:40:45 -0700	[thread overview]
Message-ID: <CAA9f-OfcRBrboUp-+UPUduPyLufRTeBt+JT4=C7-fTYzQ9dVTw@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9oB5j3u20ePPouhOydb-GehgY6JRsE+mNs+CSs=KDb=tQ@mail.gmail.com>

On Thu, Jun 15, 2017 at 7:44 PM, 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.

Many thanks, that's really helpful :-)

>
> What use case did you have in mind, anyway, for old tags?

Often the only record I will keep of the version I've built/am running
is the tag name. Of course this means my process is deficient, I just
thought that there was little downside to keeping them around.

>
> Jason
>

      parent reply	other threads:[~2017-06-16 16:26 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
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 [this message]

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='CAA9f-OfcRBrboUp-+UPUduPyLufRTeBt+JT4=C7-fTYzQ9dVTw@mail.gmail.com' \
    --to=oliver@monzo.com \
    --cc=Jason@zx2c4.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).