From: "Wesley J. Landaker" <wjl@icecavern.net>
To: Chris Patti <cpatti@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Symbolic 'references' in Git?
Date: Thu, 14 Apr 2011 15:24:14 -0600 [thread overview]
Message-ID: <201104141524.15212.wjl@icecavern.net> (raw)
In-Reply-To: <BANLkTinV8niLibzOQRVraYqwB0hKW1=r1w@mail.gmail.com>
On Thursday, April 14, 2011 14:30:59 Chris Patti wrote:
> We want a way to have our Bamboo configuration utilize a symbol to
> refer to 'latest release' 'latest patch' etc. in Git, rather than
> having to go in and change the actual branch name every time we ship a
> release and create a new one.
>
> We thought about using something like:
>
> git symbolic-ref -m'new next-release branch build for Bamboo'
> next-release release-3.15
>
> However, this symbolic ref is only local to one repository, and we
> want it to be global across all of Bamboo.
>
> Rather than resorting to manually copying the symbolic ref file
> around, from repo to repo, is there any way to make such a symbolic
> 'variable' global?
Why not just use a tag or a branch ?
git tag -F next-release release-3.15
OR
git branch -D next-release
git branch next-release release-3.15
(I personally think branches are nicer for this since tags are "supposed" to
be immutable.)
next prev parent reply other threads:[~2011-04-14 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 20:30 Symbolic 'references' in Git? Chris Patti
2011-04-14 21:24 ` Wesley J. Landaker [this message]
2011-04-14 21:31 ` Chris Patti
2011-04-14 22:20 ` Jeff King
2011-04-14 22:22 ` Wesley J. Landaker
2011-04-14 23:00 ` Junio C Hamano
2011-04-15 8:27 ` Michael J Gruber
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=201104141524.15212.wjl@icecavern.net \
--to=wjl@icecavern.net \
--cc=cpatti@gmail.com \
--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).