From: Vladimir Sizikov <vsizikov@...>
Date: 2010-02-28T04:14:44+09:00
Subject: [ruby-core:28363] Re: [ANN] Toward rich diversity of Ruby 	development.

Hi,

We had the same problem initially, but it was solved with some
gitconfig magic, something like this:

[remote "origin"]
        url = git@github.com:rubyspec/matzruby.git
        push = refs/remotes/trunk:refs/heads/trunk
        push = refs/remotes/ruby_1_9_1:refs/heads/ruby_1_9_1
        push = refs/remotes/mvm:refs/heads/mvm
        push = refs/remotes/ruby_1_8:refs/heads/ruby_1_8
        push = refs/remotes/ruby_1_8_7:refs/heads/ruby_1_8_7
        push = refs/remotes/ruby_1_8_6:refs/heads/ruby_1_8_6
        push = refs/remotes/ruby_1_8_5:refs/heads/ruby_1_8_5
        push = refs/remotes/ruby_1_6:refs/heads/ruby_1_6
        push = refs/remotes/ruby_1_4:refs/heads/ruby_1_4
        push = refs/remotes/ruby_1_3:refs/heads/ruby_1_3
        push = refs/remotes/tags/*:refs/tags/*

Adjusting the 'push' values it is possible to control where to push to.

On Sat, Feb 27, 2010 at 6:30 PM, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:
> But yes, this is ugly. �Should we move those branches into tags? �I'm in
> neutral on this point.

Personally, I think that having separate proper branches and proper
tags seems to be pretty useful. There are only handful of important
branches and having them separated from countless and less-important
tags is good.

So that 'git branch -a' would print only important branches and 'git
tag -l' would print the tags.

Thanks,
  --Vladimir