Re: [Valgrind-developers] branch backports?

[Julian S. <js...@ac...>]

> > >> My only concern is that it would be good to have an official tracking
> > >> mechanism for which changes have been backported and which are
> > >> outstanding.
> > >
> > > So I made this file 3_0_BUGSTATUS.txt which I hoped would be at
> > > least a step in that direction.  I do want to keep careful track
> > > of what the bug status is and what's outstanding.
> >
> > Hmm, I think using SVN rather than CVS is a huge win here, because we can
> > refer to individual bugfixes with a single revision number, ie. have a
> > list of "to be merged" revisions.
>
> That's partly why I started noting the SVN revision for a fix when
> closing bugs, and likewise with the bug number in the SVN log.

That's great, but .. could you also update 3_0_BUGSTATUS.txt with
that info upon closing a bug, so all the relevant info is in one
place?

J