git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Symbolic 'references' in Git?

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Apr 15, 2011, 08:27 UTC
Message-ID
<4DA80162.1070703@drmicha.warpmail.net>
In-Reply-To
<BANLkTik5tD5UOrDkpL8ahEgwFjT+suHACQ@mail.gmail.com>
Chris Patti venit, vidit, dixit 14.04.2011 23:31:
Show 38 quoted lines
> On Thu, Apr 14, 2011 at 5:24 PM, Wesley J. Landaker <wjl@icecavern.net> wrote:
>> 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.)
>>
> 
> 
> Won't either of those things create a 'next-release' that's frozen in
> time where the release-3.15 branch is *right now*?
> 
> This is for a CI system (Bamboo) so we need next-release to act as if
> we were using release-3.15 itself.
Maybe add a refspec
refs/heads/release-3.15:refs/heads/release

which ensures that you push that branch out under two names? When you (integrator/release manager) switch to a different release branch you just need to change your config (and probably push -f).

Michael
Previous: Junio C Hamano
Message 7 of 7 in “Symbolic 'references' in Git?”
  1. Chris PattiApr 14, 2011
  2. Wesley J. LandakerApr 14, 2011
  3. Chris PattiApr 14, 2011
  4. Jeff KingApr 14, 2011
  5. Wesley J. LandakerApr 14, 2011
  6. Junio C HamanoApr 14, 2011
  7. Michael J GruberApr 15, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.