git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [StGit RFC] Make "stg branch -l" faster by getting all git config information in one call

From
David Kågedal <davidk@lysator.liu.se>
Date
Dec 13, 2007, 14:15 UTC
Message-ID
<87odcur88x.fsf@lysator.liu.se>
In-Reply-To
<b0943d9e0712130604r6daf05d5n7afbadfe23831839@mail.gmail.com>
"Catalin Marinas" <catalin.marinas@gmail.com> writes:
Show 15 quoted lines
> 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.

If you remove everything but the branch name, you will have identical output to "git branch", but much slower. Then there is no reason to use it. The reason I used "stg branch -l" was that I found it interesting to know which branches I had initialized with stgit, and I could see uses for the description as well.

-- 
David Kågedal
Previous: Catalin MarinasNext: David Kågedal
Message 5 of 13 in “[StGit RFC] Make "stg branch -l" faster by getting all git config information in one call”
  1. David KågedalDec 13, 2007
  2. git config --get-regexp exit statusDavid Kågedal, Dec 13, 2007
  3. Junio C HamanoDec 13, 2007
  4. Catalin MarinasDec 13, 2007
  5. David KågedalDec 13, 2007
  6. David KågedalDec 13, 2007
  7. Catalin MarinasDec 13, 2007
  8. David KågedalDec 13, 2007
  9. Karl HasselströmDec 13, 2007
  10. Karl HasselströmDec 13, 2007
  11. Catalin MarinasDec 13, 2007
  12. David KågedalDec 13, 2007
  13. Karl HasselströmDec 13, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.