Comment 1 by Loïc d'Anterroches, May 12, 2010

Effectively, as soon as one have many branches, this would help a 
lot.

Comment 2 by Sylvestre Ledru, Sep 21, 2010

As a daily user of Indefero, I agree that it is a "must 
have" feature!

Comment 3 by Thomas Keller, Nov 17, 2010

I pushed some initial work in commit 70e8d12 - I'm not convinced 
that the way I did it for git is the best way, so improvements are 
welcome here.

For subversion I think there is hardly a proper way to list 
"branches", simply because subversion has no such concet. 
And since the getCommit() API method does not provide us with a 
partial path or anything we could use to extract the underlying 
"used" branch, the only other hack I can think of would be 
using the -v option to svn log and iterate over the changed files, 
while noting distinct "/(trunk)" and 
"/branches/([^\/]+)" entries. I don't know how useful this 
is, especially since the changed paths are directly outputted a few 
lines below anyways.

Comment 4 by Thomas Keller, Nov 24, 2010

Loic, any feedback?

Comment 5 by Thomas Keller, Nov 25, 2010

Comment 6 by Loïc d'Anterroches, Nov 29, 2010

Subversion would be messy, effectively it means parsing the paths of 
all the touched files and collect the /branches/*/ info. And this 
would work only if the project is following the "standard" 
layout. So, you can forget it for the moment. For the others, this 
is fine, git has the inBranches command, so we can use it.

Comment 7 by Loïc d'Anterroches, Nov 29, 2010

Short update, we will need to add the info in the 
"IDF_Commit" object to be faster. I need to do that for 
the merge history information for git, so I will take care of 
polishing this ticket. Assigned back to me.