From: Enrico Weigelt <weigelt@metux.de>
To: git <git@vger.kernel.org>
Subject: Re: How to create tags outside of refs/tags?
Date: Wed, 23 Feb 2011 17:36:35 +0100 [thread overview]
Message-ID: <20110223163634.GA16569@nibiru.local> (raw)
In-Reply-To: <7v7hcrewyz.fsf@alter.siamese.dyndns.org>
* Junio C Hamano <gitster@pobox.com> wrote:
Hi folks,
> I would think that using a private namespace other than tags for your own
> use (e.g. "git update-ref refs/anchor/release-20110222 $that_commit") may
> be the best option that is easiest to understand, though.
I'm doing similar things with source crawlers in the OSS-QM
project: each time a new upstream version arrives, it gets
tag into a queue namespace, so I can pick them up an do my
usual qm works on them one by one.
git ls-remote git://pubgit.metux.de/oss-qm/glib2.git | grep queue
cu
--
----------------------------------------------------------------------
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
----------------------------------------------------------------------
next prev parent reply other threads:[~2011-02-23 16:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 17:21 How to create tags outside of refs/tags? Christian Halstrick
2011-02-21 17:48 ` Jay Soffian
2011-02-21 23:52 ` Junio C Hamano
2011-02-22 6:17 ` Christian Halstrick
2011-02-22 8:03 ` Jeff King
2011-02-22 8:09 ` Junio C Hamano
2011-02-22 8:14 ` Jeff King
2011-02-22 10:09 ` Jakub Narebski
2011-02-22 15:27 ` Jeff King
2011-02-22 16:21 ` Christian Halstrick
2011-02-22 18:38 ` Junio C Hamano
2011-02-22 22:08 ` Christian Halstrick
2011-02-23 12:42 ` Michael J Gruber
2011-02-23 13:45 ` Christian Halstrick
2011-02-23 16:36 ` Enrico Weigelt [this message]
2011-02-22 15:06 ` Jay Soffian
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=20110223163634.GA16569@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).