From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "David Kågedal" <davidk@lysator.liu.se>
Cc: git@vger.kernel.org
Subject: Re: [StGit RFC] Make "stg branch -l" faster by getting all git config information in one call
Date: Thu, 13 Dec 2007 14:04:26 +0000 [thread overview]
Message-ID: <b0943d9e0712130604r6daf05d5n7afbadfe23831839@mail.gmail.com> (raw)
In-Reply-To: <20071213133653.13925.89254.stgit@krank>
On 13/12/2007, David Kågedal <davidk@lysator.liu.se> wrote:
> I have a fair amount of branches, and I noticed that "stg branch -l"
> takes ridiculously long to finish.
I have the same problem.
> Maybe someone can help me find a quicker replacement for the
> get_protected call?
We can have the standard --list command which ignores the protected
flag or even the stgit.formatversion. Just a simple listing of the
branches (that's what I need most of the time). To get the
description, the 's' and 'p' flags, we could use --list-full or
something similar and wait a bit longer. This would also improve the
bash completion of commands taking branch names as arguments.
We had a similar issue in the past with 'series' as it was checking
whether the patch is empty. We ended up adding a '--empty' option for
this case.
--
Catalin
next prev parent reply other threads:[~2007-12-13 14:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 13:38 [StGit RFC] Make "stg branch -l" faster by getting all git config information in one call David Kågedal
2007-12-13 13:42 ` git config --get-regexp exit status David Kågedal
2007-12-13 18:06 ` Junio C Hamano
2007-12-13 14:04 ` Catalin Marinas [this message]
2007-12-13 14:15 ` [StGit RFC] Make "stg branch -l" faster by getting all git config information in one call David Kågedal
2007-12-13 14:31 ` David Kågedal
2007-12-13 15:38 ` Catalin Marinas
2007-12-13 16:08 ` David Kågedal
2007-12-13 16:08 ` Karl Hasselström
2007-12-13 16:04 ` Karl Hasselström
2007-12-13 16:10 ` Catalin Marinas
2007-12-13 16:39 ` David Kågedal
2007-12-13 17:04 ` Karl Hasselström
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=b0943d9e0712130604r6daf05d5n7afbadfe23831839@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=davidk@lysator.liu.se \
--cc=git@vger.kernel.org \
/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).