On Sat, Mar 26, 2011 at 07:15, Richard Guenther <richard.guent...@gmail.com> wrote: > On Sat, Mar 26, 2011 at 11:01 AM, Florian Weimer <f...@deneb.enyo.de> wrote: >> Would something like this be useful? >> >> --- develop.html.~1.114.~ 2011-03-26 10:44:52.000000000 +0100 >> +++ develop.html 2011-03-26 10:58:49.311173994 +0100 >> @@ -434,13 +434,13 @@ >> | GCC 4.5.1 release (2010-07-31) >> GCC 4.6 Stage 3 (starts 2010-11-03) \ >> | v >> - | GCC 4.5.2 release (2010-12-16) >> + | r167945 GCC 4.5.2 release (2010-12-16) >> | >> +-- GCC 4.6 branch created ------+ >> - | \ >> + | r170934 \ >> v v >> GCC 4.7 Stage 1 (starts 2011-03-14) GCC 4.6.0 release (2011-03-25) >> - | >> + | r171512 >> | >> v >> >> The idea is to include the copy-source revision on the trunk or the >> respective branch, so that you can use the timeline to check whether a >> particular change came before or after a release. Of course, this is >> just an approximation, but it think it might still be useful. > > Uh, well - the information is readily available from SVN so I don't > think this is very useful.
I find it very useful actually. To figure out the rev at which to cut my 4.6 branch, I had to checkout gcc-4_6-branch and check the log. This would've made it slightly easier. Besides, I don't see any harm in adding this info. Diego.
