On 2012-12-05 19:43, Christian Hammond wrote:
When scanning for the right type of SCMTool for a repository, we ask
each SCMTool to try to provide information on the repository. If we can
get something useful out of it, we assume the tool is valid.

Makes sense.

The Git tool is asking for that data and is computing the tracking
branch up-front, in all cases.

That seems odd though. Maybe I miss something; if you're asking for a specific revision range, would not the first revision in the range always be the tracking branch? (It seems offhand it would be, but as I say, I'm not convinced if I miss something. If that /is/ the case, though, this would be the logical way to work around this issue.)

Also would be good to know, as this is how I am working around the issue at present.

It might be nice to only fetch when we
need it, and we know there's a lot of work that needs to be done to
refactor this code and clean it up. Would you mind filing a bug to help
us track this?



Want to help the Review Board project? Donate today at 
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to