git log master ^feature-branch about rugged HOT 2 CLOSED

You push() the master onto the walker then hide() the feature branch. An example is given of doing exactly this in the USAGE.rb file. See:

https://github.com/libgit2/rugged/blob/development/USAGE.rb#L116-132

Also, see:

https://github.com/libgit2/rugged/blob/development/README.md#refs

if you have any confusion about how to get the master and feature-branch refs for the Walker.

from rugged.

Oh! Thanks for the quick reply. So this is to say that there is no interface to git log, so to generate that list, I will need to (1) get a complete list of refs in feature-branch (which, since it's branched off master will be ~20,000), then iterate through every ref in master (~20,000) and see if it is contained by the array of commits in my feature branch. Right? Or am I missing something here?

But maybe I have bigger problems. Attempting various things from the Readme and Usage docs yields various exceptions:

ruby-1.9.3-p194 :003 > repo.refs(/tags/)
ArgumentError: wrong number of arguments (1 for 0)

ruby-1.9.3-p194 :009 > repo.loookup "779fbb1e17e666832773a9825875300ea736c2da"
NoMethodError: undefined method `loookup' for #<Rugged::Repository:0x007fa5eb847a18>

ruby-1.9.3-p194 :022 > Rugged::Version
=> "0.16.0"

Is it possible the docs have been updated to reflect new functionality but the gem version didn't get bumped?
Also couldn't find doc for Rugged::Repository#refs in the rdoc, class appears to simply be Enumerator.

ruby-1.9.3-p194 :027 > repo.refs.class
 => Enumerator 

from rugged.