Hi, Gmail has been acting up, I couldnt send the mail I wanted to yesterday, anyway there was a big commit yesterday. I actually had work that overlapped with Peter's previous commit, hence had to merge them and ensure the commit went right. Vg still does not compile, but we are getting there, *again* sigh. I think that we need a different approach to commits.
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? Peter I have answered your question about do_pipe_inner in the code. sys_pipe's semantics differ on linux and netbsd, do_pipe_inner is a stub to convert the semantics back and forth. Instead of having VG_(pipe) take different arguments and littering code all over. I might have based it on netbsd's linux emu implementation. I forget if I did. Is it possible to get svn to write to our ML. Anyone done this before? Regards, Kailash _______________________________________________ Vg4nbsd-devel mailing list [email protected] http://lists.berlios.de/mailman/listinfo/vg4nbsd-devel
