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

Re: How to keep different version numbers in different branches?

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Apr 5, 2010, 18:15 UTC
Message-ID
<vpqhbnprcj0.fsf@bauges.imag.fr>
In-Reply-To
<hpcscv$umg$3@dough.gmane.org>
Stephen Kelly <steveire@gmail.com> writes:
Show 11 quoted lines
> Hi,
>
> My project uses git and so far has only one branch, 'master'.
>
> http://gitorious.org/grantlee/grantlee
>
> I want to make a 0.1 release, so that would mean creating a 0.1 branch and 
> updating files contained in the branch such as the README file and the CMake 
> files and the api documentation to report version 0.1.0, and creating the 
> 0.1.0 tag. The next tag on that branch would be 0.1.1 etc. Simultaneously, 
> the version number in those files is changes to 0.2.0 in the master branch.

You can have this number generated by your build script instead of having to commit it. See what git does, for example. The command "git describe" should help.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Christian MICHONNext: Avery Pennarun
Message 3 of 9 in “How to keep different version numbers in different branches?”
  1. Stephen KellyApr 5, 2010
  2. Christian MICHONApr 5, 2010
  3. Matthieu MoyApr 5, 2010
  4. Avery PennarunApr 5, 2010
  5. Matthieu MoyApr 5, 2010
  6. Avery PennarunApr 5, 2010
  7. Stephen KellyApr 6, 2010
  8. Steven MichalskeApr 6, 2010
  9. Junio C HamanoApr 5, 2010

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.