newlib-2_2_0 tag missing?
Wed Mar 25 21:46:00 GMT 2015
On Mar 24 14:20, Freddie Chopin wrote:
> 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.
That's how cvs2git created the stuff. Since nobody is going to pick
up the old "branches which should have been tags" and changes them,
they should work for the purpose. In the future, I'm sure Jeff will
create the usual tags.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 819 bytes
Desc: not available
More information about the Newlib