From: Enrico Weigelt <weigelt@metux.de>
To: git@vger.kernel.org
Subject: Re: Why git tags are there in git?
Date: Sat, 29 Jan 2011 18:17:51 +0100 [thread overview]
Message-ID: <20110129171750.GA602@nibiru.local> (raw)
In-Reply-To: <1296214676536-5969544.post@n2.nabble.com>
* vikram2rhyme <vikram2rhyme@gmail.com> wrote:
Hi,
> I am wondering why the tags are there in git. As they are just
> pointer to the commit we can refer those commit by SHA sum only
> then why tagging? Moreover a commit can be tagged more than once
> that result in multiple tags pointing to the same point in the history.
> Is this a design flaw?
No, it's an important design aspect.
Tag references (not to be mixed up w/ tag objects) are very useful
to add a conveniently named pointer to some object (not necessarily
a commit), so humans as well as programs can easily find them.
For example, in my OSS-QM repositories [1], I have some robots
importing releases (sometimes from upstream's git repos, sometimes
from foreign VCSs, tarballs or even distro packages) and tag
them into a normalized namespace, so automatic systems (eg. my
Briegel buildsystem) can easily fetch sourcetrees from there
w/o further manual tweaking.
cu
[1] http://www.metux.de/download/oss-qm/normalized_repository.pdf
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
prev parent reply other threads:[~2011-01-29 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 11:37 Why git tags are there in git? vikram2rhyme
2011-01-28 12:27 ` "L. Alberto Giménez"
2011-01-28 15:03 ` Gabriel Filion
2011-01-28 16:06 ` Konstantin Khomoutov
2011-01-29 17:17 ` Enrico Weigelt [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=20110129171750.GA602@nibiru.local \
--to=weigelt@metux.de \
--cc=git@vger.kernel.org \
/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).