> This would be a good time to ask about how to prepare and send
> patches, i.e., what you want for these (re)additions.

# merge any other changes that happened in the meantime
cd VEX
svn up
cd ..

# remake, re-test

# generate diff
cd VEX
svn diff -rHEAD

# send the diff

One thing though.  Bugs discussed on mailing lists tend to get
forgotten or otherwise fall through the cracks.  A much more reliable
approach, if you have bugs/patches in future, is to file a bug as
described at http://valgrind.org/support/bug_reports.html
and do all the discussion, patches, patch reviewing etc in the bug
report.

J

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to