From: Michael J Gruber <git@drmicha.warpmail.net>
To: Christian Halstrick <christian.halstrick@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Jakub Narebski <jnareb@gmail.com>, git <git@vger.kernel.org>
Subject: Re: How to create tags outside of refs/tags?
Date: Wed, 23 Feb 2011 13:42:45 +0100 [thread overview]
Message-ID: <4D6500C5.7020803@drmicha.warpmail.net> (raw)
In-Reply-To: <AANLkTiki9W_mJKLON+punKJLDWx5rmQdZ3bS16zadYFj@mail.gmail.com>
Christian Halstrick venit, vidit, dixit 22.02.2011 23:08:
> Hi,
>
>> How about taking advantage of the fact that you do not have to treat tag
>> namespace as a global thing? For the "release tool" to "get a commit ID"
>> and do something useful, the "release tool" must be working on a git
>> repository, and hopefully that repository is something other than the ones
>> developers directly play with (by checking out random branches in its
>> working tree and compiling, etc.).
>
> These assumptions are all correct. The "release tool" works on his clone
> of a central repo. The release tool may even modify the content (e.g. increasing
> release numbers in project metadata files) and create new git commits.
> In the end it wants to create tags/refs locally und push these tags back
> so that in the central repo the commits are not gc'ed.
>
> Something like:
>
> cd <releaseRepo>
> git fetch origin
> git checkout <commitIdToRelease>
> edit pom.xml; git add pom.xml
> git commit -m "release ..."
> git tag <releaseName>
> git push origin 'refs/tags/<releaseName>:refs/releases/<releaseName>'
>
> should do the job, or?
Yep. Also, if you do
git tag release/<releasename>
then a simple push refspec 'refs/tags/release/*:refs/releases/*' in your
config does the job. (Assuming you don't have any other tags in release/.)
Michael
next prev parent reply other threads:[~2011-02-23 12:46 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 [this message]
2011-02-23 13:45 ` Christian Halstrick
2011-02-23 16:36 ` Enrico Weigelt
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=4D6500C5.7020803@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=christian.halstrick@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=peff@peff.net \
/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).