On Tue, 2012-01-24 at 11:45 -0500, Steven Rostedt wrote: > $ git tag | grep -- -rt > v3.0.10-rt27 > v3.0.10-rt27-rebase > v3.0.11-rt28 > v3.0.11-rt28-rebase > v3.0.12-rt29 > v3.0.12-rt29-rebase > v3.0.12-rt30 > v3.0.12-rt30-rebase > v3.0.14-rt31 > v3.0.14-rt31-rebase > v3.0.14-rt32 > v3.0.14-rt32-rebase > v3.0.17-rt33 > v3.0.17-rt33-rebase > v3.0.9-rt25 > v3.0.9-rt26 > As I found out by testing what was pushed and not seeing what I expected and going crazy in the mean time, I've discovered (thanks to the guys on Freenode #git) that tags of commits that are not associated to any branch (like these are) will not be pulled with a normal "git fetch" or "git remote update". You need to do a "git fetch --tags" to get the tags for the rebases that are no long part of the v3.0-rt-rebase branch. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
