From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] branch: only print upstream relationship with -v -v
Date: Thu, 18 Mar 2010 07:06:41 +0700 [thread overview]
Message-ID: <fcaeb9bf1003171706s31870438kc69606389495876d@mail.gmail.com> (raw)
In-Reply-To: <7vwrxavqig.fsf@alter.siamese.dyndns.org>
On 3/17/10, Junio C Hamano <gitster@pobox.com> wrote:
> Nguyễn Thái Ngọc Duy <pclouds@gmail.com> 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
prev parent reply other threads:[~2010-03-18 0:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 15:05 [PATCH] branch: only print upstream relationship with -v -v Nguyễn Thái Ngọc Duy
2010-03-17 16:21 ` Michael J Gruber
2010-03-17 16:53 ` Junio C Hamano
2010-03-18 0:06 ` Nguyen Thai Ngoc Duy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fcaeb9bf1003171706s31870438kc69606389495876d@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).