Re: [Erlyaws-list] No git tag for yaws 1.81 release?

[Hans U. N. <hu...@n-...>]

On Fri, 13 Mar 2009 19:22:43 +0100
Wojciech Kaczmarek <kac...@gm...> wrote:

> I guess it is so because git tags, even annotated, don't get pushed
> from your local repo to remote one unless you do git push --mirror or
> reconfigure which of your local refs are to be pushed. At least it's
> what I had with my github repositories.
> 
> So the quick&dirty solution is that Klacke or other maintainer would
> do push --mirror once from his local repository where the tags are
> present.

Uhm. "git push --mirror" will push ALL local branches and tags, which
might be quite a lot more than what is actually wanted.

And now that I am looking at it more closely... perhaps it would be
useful to add git tags for the older releases as well.

If Klacke uses a tag naming scheme like "release/yaws-1.81", then
setting up a second push revspec with something like

  $ git config --add remote.origin.push \
        "refs/tags/release/*:refs/tags/release/*"

should make a simple "git push origin" do the job. (Even if github.com
has a bug which breaks some of the hyperlinks to tags containing a "/".)

Going without "/" in the tags and using "refs/tags/*:refs/tags/*" is
also possible. However, that would push all of Klacke's local git tags
all the time, not just the release ones.

I guess Klacke still has the branches git-svn has created for the SVN
tags, to which the proper tags could be added. If not, it should be
possible to find out the SVN revision number for the releases, and use
git-svn-id: in the git log messages to find the proper git commits.

-- 
Hans Ulrich Niedermann