Hi,
> How'd that happen? It's always a good idea to start the day by doing an > update and checkin when you finish for the day. That way, nobody does > any double work. That's just a waste of resources, IMHO. > Yes, the problem was that i was working on it the previous night, but broke m_main.c. I had to redo the diffs. Its still incomplete by the way. I didnt commit because of that. > > Vg still does not compile, but we are getting there, *again* sigh. I > > think that we need a different approach to commits. > > Perhaps that's a good idea. > > > I propose that any further changes to valgrind, by us should be > > encapsulated in > > /* vg4nbsd */ > > /* !vg4nbsd */ comments. > > We may work on arch indep things, so VGO_netbsdelf2 ifdefs may always > > not indicate where our changes are. This makes us clear when we have > > changed logic. > > Lets do this going forward? > > Is this really necessary? We should let our tools do this for us. For > example, we could tag (copy to /tags) after we finish synching with a > version of Valgrind main code. Then we can simply do svn diff on the > trunk and the tag to see what has changed in between. > > What are your thoughts on this? > Sounds like a plan. However will it be easily visible when we do the next sync? Rather than doing an svn diff to check and then check against another diff? > It's possible alright, just like with CVS. Valgrind does this too, right? > I've never done it though, so I wouldn't know where to begin. Will look into it. _______________________________________________ Vg4nbsd-devel mailing list [email protected] http://lists.berlios.de/mailman/listinfo/vg4nbsd-devel
