2017-02-25 1:53 GMT+01:00 Austin English <austinengl...@gmail.com>:
> Hi Ivo,
>
> I'm very excited for the git move! I tested for
> https://bugs.kde.org/show_bug.cgi?id=352395, which I rely upon to keep
> track of precisely which version of Valgrind I'm testing with
> (especially useful for historical logs).
>
> With git, this is broken:
> austin@austin2:/tmp/valgrind$ ./vg-in-place -v --version
> valgrind-3.13.0.SVN-unknown-vex-unknown
>
> That said, checking out / compiling went great! ;)

Hi Austin,

Thank you for your feedback!
Indeed, svn related commands must be replaced with git ones.
Can you propose a patch? I assume instead of SVN revisions
we need to get git commit ids.
I will have a look at the other Valgrind parts.

I.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to