mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <>
To: anatoly techtonik <>
Cc: "Ævar Arnfjörð Bjarmason" <>,
	"Randall S. Becker" <>,
	"Git Mailing List" <>,
	"Igor Djordjevic" <>
Subject: Re: Unify annotated and non-annotated tags
Date: Sat, 02 Dec 2017 21:54:40 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (anatoly techtonik's message of "Sun, 3 Dec 2017 00:26:59 +0300")

anatoly techtonik <> writes:

>> Git is not doomed to preserve anything forever. We've gradually broken
>> backwards compatibility for a few core things like these.
>> However, just as a bystander reading this thread I haven't seen any
>> compelling reason for why these should be removed. You initially had
>> questions about how to extract info about them, which you got answers
>> to.
>> So what reasons remain for why they need to be removed?
> To reduce complexity and prior knowledge when dealing with Git tags.

Then you are barking up a wrong tree, I would have to say.  If you
do not think non-annotated tags are serving any good purpose in the
context of _a_ project you are involved in and making your life
miserable because some tags are and other tags are not annotated,
suggest to _that_ project to refrain from using non-annotated tags.

Projects that do use non-annotated tags have chosen to use them for
reasons of their own.  It may be that these tags could be annotated
tags instead for some projects, and depending on their tooling there
might be no downside in switching.  Or they may have chosen to use
non-annotated tags for reasons that you do not know.

  parent reply	other threads:[~2017-12-03  5:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2017-11-23 15:08 ` Re: Unify annotated and non-annotated tags Randall S. Becker
2017-11-23 21:24   ` Thomas Braun
2017-11-24  9:52   ` anatoly techtonik
2017-11-24 10:24     ` Ævar Arnfjörð Bjarmason
2017-12-02 21:26       ` anatoly techtonik
2017-12-02 22:25         ` Philip Oakley
2017-12-23 13:41           ` anatoly techtonik
2017-12-24 12:31             ` Philip Oakley
2017-12-03  5:54         ` Junio C Hamano [this message]
2017-11-24 14:11     ` Randall S. Becker
2017-11-10 10:58 anatoly techtonik
2017-11-11  1:46 ` Igor Djordjevic
2017-11-11  2:06   ` Junio C Hamano
2017-11-11  2:50     ` Igor Djordjevic
2017-11-23  7:31     ` anatoly techtonik
2017-12-23 13:33     ` anatoly techtonik

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).