Junio C Hamano <junkio@xxxxxxx> wrote: > Eric Wong <normalperson@xxxxxxxx> writes: > > > Adam Roben <aroben@xxxxxxxxx> wrote: > >> This patch adds a new 'find-rev' command to git-svn that lets you easily > >> translate between SVN revision numbers and git tree-ish. > > > > Looks useful. > > > > Acked-by: Eric Wong <normalperson@xxxxxxxx> > > But looks quite wasteful. Why not run "rev-list -v" or > something instead of running cat-file on revision one-by-one? Didn't know about "rev-list -v", but I just checked and it still has the limited-size buffer that --pretty=raw has. "git-svn log" only runs cat-file if it can't find a git-svn-id: line at the bottom. (I used log --abbrev-commit --pretty=raw). Sorry about the premature Ack, I hadn't had my coffee yet at that point (and now I'm half awake :x) Adam: However, since we're not fetching ranges... You can do $gs->rev_db_get($rev_nr) to easily find a commit given a revision. Bonus points if this works independently of the current HEAD so you can look up revision numbers on different branches. (git-svn log should be made to support this, too) -- Eric Wong - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html