On Monday 02 November 2009, Øyvind Harboe wrote:
> I don't know when 2646 was compared to 0.2... Don't know offhand
> how to check that w/git.
As I noted earlier: "git log", then use the search
mechanism to find "@2646" ... which points to:
> > That SVN id matches
> > efef05870d726fe4cb6786d785fae4628fe7ec1e, also
> > known to "git describe" as v0.2.0-125-gefef058;
That is, "git describe efef05870d726fe4cb6786d785fae4628fe7ec1e"
will tell you that it's 125 commits after the v0.2.0 tag.
> > so it happened 125 commits into the 450+ which
> > preceded the RC0 tag.
Since you said something about confusion between
the git-svn comments like
restore ICE watchpoint registers when the *last* software breakpoint is
removed
git-svn-id: svn://svn.berlios.de/openocd/tr...@2646 ...deletia...
and the actual SVN r2646 type IDs, I double checked
that against the old Berlios SVN repository ... it's
got that same "restore ICE watchpoint..." comment, and
the patch contents look the same:
http://svn.berlios.de/viewvc/openocd?view=rev&revision=2646
matches "git show v0.2.0-125-gefef058".
Pieter ... from the top of a git tree, you can issue
git show v0.2.0-125-gefef058 |patch -p1 -R
to (temporarily) revert just that commit. It'll report
some noise; not clear if that implies breakage. Does
reverting that make things work for you?
- Dave
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
