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

Tagging stable releases

From
AAsaf <asafs2000@yahoo.com>
Date
Apr 14, 2009, 18:43 UTC
Message-ID
<23045562.post@talk.nabble.com>
Hello,

I'm creating many branches, checkout code, make changes, etc.. At the end, I always merge these branches to the master branch and delete them when I finish,

At the point where my local master repo seems to be stable, I push the changes to an origin repo that is public.

I guess this is a standard cycle, right?

What I'm confused about is how to tag correctly versions that are stable, Should I locally just add a tag and push the tag to the public repo?

Is it enough to use a lightweight tagging for tagging a certain commit as a release? Is it possible later on to checkout a tag, make a change and push the change into the tagged version?

Many thanks,
Asaf.
-- 
View this message in context: http://www.nabble.com/Tagging-stable-releases-tp23045562p23045562.html
Sent from the git mailing list archive at Nabble.com.
Next: Andreas Ericsson
Message 1 of 5 in “Tagging stable releases”
  1. AsafApr 14, 2009
  2. Andreas EricssonApr 15, 2009
  3. Stefan NäweApr 15, 2009
  4. Andreas EricssonApr 15, 2009
  5. Tim MazidOct 28, 2009

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.