This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: newlib-2_2_0 tag missing?
- From: Freddie Chopin <freddie_chopin at op dot pl>
- To: newlib at sourceware dot org
- Date: Tue, 24 Mar 2015 14:20:39 +0100
- Subject: Re: newlib-2_2_0 tag missing?
- Authentication-results: sourceware.org; auth=none
- References: <CDB26B51-756B-42A4-B6F0-18C8F7CA004A at mrs dot kithrup dot com> <20150324100355 dot GQ3017 at calimero dot vinschen dot de> <55115843 dot 8010004 at op dot pl> <20150324125214 dot GR3017 at calimero dot vinschen dot de>
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