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

[Q] Branch aliases (synonyms)?

From
BFBrian Foster <brian.foster@maxim-ic.com>
Date
Jul 3, 2012, 10:39 UTC
Message-ID
<1919214.YKUdgul2iY@laclwks004>
 Having fought and lost a battle not to do this,
 we are currently planning on transitioning from
 the old version (called ‘A’ below) to the new
 (called ‘B’) by creating a TEMPORARY branch for
 the new work, and at the end of the transition,
 merging it into the old, which is then the only
 branch.  That is, at the end we have something
 like the following:
            /--a---a----------\
  ...--o---o                   n---n---A (HEAD)
            \--b---b---b---b--/
 with a starting-point of:
  ...--o---A (HEAD)
 and with during-transition intermediate points
 similar to:
            /--a---A
  ...--*---*
            \--b---b---B (HEAD)
 None of which isn't a problem per se.
 The catch is a desire(? requirement?) that, when the
 transition ends, people used to using B can continue
 to use B, people used to using A can continue to use A,
 and there is no difference.  That is, after the end of
 transition, branch names A and B are the same thing.
 Always.  Automatically.
 Using a symref seems a working answer.  That is,
 after the merge, change B from a true branch head
 into a symref pointing to A:
      git merge ...
      git symbolic-ref refs/heads/B refs/heads/A
  ▶ What are the gotchas?
  ▶ Are there other solutions?
 I have written a test script to explore the idea,
 and it seems to be working.  The script is a bit
 on the long side (c.500 lines) since it is trying
 to exercise a number of different cases, so I
 won't post it unless asked.
cheers!
	-blf-
-- 
Brian Foster
Principal MTS, Software        |  La Ciotat, France
Maxim Integrated Products      |  Web:  http://www.maxim-ic.com/
Next: Hallvard Breien Furuseth
Message 1 of 11 in “[Q] Branch aliases (synonyms)?”
  1. Brian FosterJul 3, 2012
  2. Hallvard Breien FurusethJul 3, 2012
  3. Hallvard Breien FurusethJul 3, 2012
  4. Brian FosterJul 3, 2012
  5. Michael HaggertyJul 3, 2012
  6. Brian FosterJul 4, 2012
  7. Brian FosterJul 5, 2012
  8. Johan HerlandJul 3, 2012
  9. Hallvard Breien FurusethJul 3, 2012
  10. Brian FosterJul 4, 2012
  11. Hallvard Breien FurusethJul 4, 2012

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.