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

A branch question

From
JWJ. R. Westmoreland <jr@jrw.org>
Date
Mar 10, 2015, 20:56 UTC
Message-ID
<6AC11CE0-764C-4CC5-89CD-05FFB6D29EA3@jrw.org>
hi everyone
I have found a solution which may not be the best so I’m asking it here to see if I get a different solution from the wizards group. :)
I have a number of repos that were converted from svn to git. After the conversion the branches that contained each release were named something like “branches/version_<version-number>”. We want to modify the repo so the branches are named something like “release/<version-number>”. 

I currently do a command sequence like this: git checkout <existing-branch> git branch -m <existing-branch> <new-branch> git push origin :<old-branch> git push origin <new-branch> Then I do a: git checkout master git branch -D <new-branch> to cleanup my local area.

Note: These branches are only kept for historical purposes and not modified except occasionally the latest release may have an update so fix a bug.
Finally, as we move forward, what is the accepted best practice for doing a release?
Thanks in advance for your collective wisdom.

Best, J. R.

Next: Junio C Hamano
Message 1 of 3 in “A branch question”
  1. J. R. WestmorelandMar 10, 2015
  2. Junio C HamanoMar 10, 2015
  3. Junio C HamanoMar 10, 2015

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.