On 3/17/10, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Nguyễn Thái Ngọc Duy <pclouds@xxxxxxxxx> writes: > > > "git branch -v" is unusable for me because it's too slow. > > > ... > > > This is on a repository with ~30 branches, some are hundreds of > > patches behind upstream. > > > Perhaps you have an overeager branch.autosetupmerge configuration? No. Never heard of it. > I dunno. I seem to have a lot more branches than you do (currently > 56), but most of them are topics that, once they forked from a > particular commit, never merge other random commits, only because they > have new commits that are unrelated to the objective of the topic, so > most of my branches do not have "upstream" in that sense. I did sysprof and it seems half the time was spent inside merge_bases_many(). Being a complete ignorant about merging stuff, I put "return NULL;" at the beginning of that function, "git branch -v" now goes down to 2 seconds. Don't know if that could tell anything. -- Duy -- 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