newlib-2_2_0 tag missing?

Freddie Chopin freddie_chopin@op.pl
Tue Mar 24 13:45:00 GMT 2015


On 03/24/2015 01:52 PM, Corinna Vinschen wrote:
> Ok, I'm not that familiar with git yet, so I don't grok where the 
> newlib-2_1_0 commit comes from, but I see a newlib-2_2_0 tag (or 
> branch, whatever) in the repo which appears to point to the right 
> thing, no? 
> https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;a=shortlog;h=refs/heads/newlib-2_2_0

Well, that's a branch named "newlib-2_2_0", but there is no tag. A 
branch is useful if you plan to backport some fixes from master branch 
to 2.2.x release branch (to release 2.2.1 with a fix but without other 
unrelated changes from the master branch). A tag is just a "marker" for 
a specific commit (in any branch) that says "this particular commit is 
important". In case of newlib I don't think release branches would be 
useful.

Regards,
FCh



More information about the Newlib mailing list