newlib-2_2_0 tag missing?
Mon Mar 30 14:20:00 GMT 2015
On Mar 28 03:27, Mike Frysinger wrote:
> On 24 Mar 2015 14:44, Corinna Vinschen wrote:
> > 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.
> usually people go through and make them into tags. even it's as simple as
> `mv .git/refs/heads/newlib-* .git/refs/tags/`. that could be done locally
> too though by something like (untested):
> git tag newlib-2_1_0 remotes/origin/newlib-2_1_0
> git push origin :newlib-2_1_0
> git push origin --tags
I don't trust my git skills enough to make such changes. If it works
for you, feel free to apply these changes to convert release branches
to release tags.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 819 bytes
Desc: not available
More information about the Newlib