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

Re: Symbolic 'references' in Git?

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 14, 2011, 23:00 UTC
Message-ID
<7vd3kofnf9.fsf@alter.siamese.dyndns.org>
In-Reply-To
<BANLkTik5tD5UOrDkpL8ahEgwFjT+suHACQ@mail.gmail.com>
Chris Patti <cpatti@gmail.com> writes:
Show 8 quoted lines
>> 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*?

I suspect that most people go about this the other way around. You keep the next-release branch that goes forward, and your automated process would follow that one. When you really cut a release, you tag the tip of next-release, i.e. "git tag v3.15 next-release", to give it a name.

Previous: Wesley J. LandakerNext: Michael J Gruber
Message 6 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.