Re: Why git tags are there in git?
- From
- Enrico Weigelt <weigelt@metux.de>
- Date
- Jan 29, 2011, 17:17 UTC
- Message-ID
- <20110129171750.GA602@nibiru.local>
- In-Reply-To
- <1296214676536-5969544.post@n2.nabble.com>
* vikram2rhyme <vikram2rhyme@gmail.com> wrote:
Hi,
Show 5 quoted lines
> 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 ----------------------------------------------------------------------