Choosing the qt tree to file merge requests

[David Faure]

On Monday 14 September 2009, Thiago Macieira wrote:
> Create a branch off the tag:
> 
>         git branch 4.6-tp1 v4.6.0-tp1

-obelix- dfaure 18:21 /d/qt/4/kde-qt (4.5.2-patched)>git branch 4.6-tp1 v4.6.0-tp1
fatal: Not a valid object name: 'v4.6.0-tp1'.

> > `git checkout v4.6.0-tp1` or `git checkout tags/v4.6.0-tp1` doesn't work,
> 
> Either should work.

-obelix- dfaure 17:56 /d/qt/4/kde-qt (4.5.2-patched)>git checkout v4.6.0-tp1                
error: pathspec 'v4.6.0-tp1' did not match any file(s) known to git. 

-obelix- dfaure 17:55 /d/qt/4/kde-qt (4.5.2-patched)>git checkout tags/v4.6.0-tp1
error: pathspec 'tags/v4.6.0-tp1' did not match any file(s) known to git. 

> Tags are global. As soon as you fetched it, it should appear in "git tag".

But how does one list tags in the first place? The only way is to be told the tag name by email??

> I recommend people track the unmodified qt.git branches 4.6 or 4.6-stable.

So I'm barking up the wrong tree in the first place? Why push a tag if that's not
what you recommend we use?

-- 
David Faure, faure at kde.org, sponsored by Nokia to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).