1 | | git branches are like hg bookmarks (well, it's even the other way round, historically). Now the fact that, in Trac, we propagate that information to the ancestors is quite arbitrary. It is convenient when you follow a topic branch like here, but only up to a point, i.e. it gets //really// annoying when you go deep in the past, as then you have basically the list of all branches for each changeset (see ... well I //thought// I created a ticket for that, can't find it). There must be something smarter to do. |
| 1 | git branches are like hg bookmarks (well, it's even the other way round, historically), so it's just an external pointer to a given commit (in git terms, this pointer is a "ref"). Now the fact that, in Trac, we propagate that information to the ancestors is quite arbitrary. It is convenient when you follow a topic branch like here, but only up to a point, i.e. it gets //really// annoying when you go deep in the past, as then you have basically the list of all branches for each changeset (see ... well I //thought// I created a ticket for that, can't find it). There must be something smarter to do. |