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

Re: GIT - releases workflow

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 12, 2006, 22:54 UTC
Message-ID
<Pine.LNX.4.63.0612122353320.2807@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<89b129c60612121444t18ba94ecv57eea4c72be1663a@mail.gmail.com>
Hi,
On Tue, 12 Dec 2006, Sean Kelley wrote:
> I was wondering if anyone could share ideas on how best to use GIT to 
> handle releases for those working with a remote GIT repository?  Do you 
> create a branch and push it to the remote?  Thus you have a new branch 
> referencing the particular release?
Why not just tag the release, and push the tag?

Hth, Dscho

Previous: Sean KelleyNext: Matthias Kestenholz
Message 2 of 10 in “GIT - releases workflow”
  1. Sean KelleyDec 12, 2006
  2. Johannes SchindelinDec 12, 2006
  3. Matthias KestenholzDec 13, 2006
  4. Johannes SchindelinDec 13, 2006
  5. Shawn PearceDec 13, 2006
  6. Shawn PearceDec 13, 2006
  7. Sean KelleyDec 13, 2006
  8. Sean KelleyDec 13, 2006
  9. Andreas EricssonDec 13, 2006
  10. Linus TorvaldsDec 13, 2006

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.