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

Re: [PATCH] rebase: introduce --update-branches option

From
WHWarren He <pickydaemon@gmail.com>
Date
Sep 7, 2019, 23:41 UTC
Message-ID
<20190907234146.1473-1-wh109@yahoo.com>
In-Reply-To
<20190903013959.GA40029@syl.lan>

Brian, thanks for looking. The only thing I can come up with to say about having lots of refs is that at least that part of this isn't brand new code. The part that collects ref info uses the same routines as `git log --decorate`. Do you recall how long that took in the repository with 80,000 refs?

Junio, thanks for eyeballing. Let me know if some style violations remain.

Taylor, thanks for coming up with a way to configure branches to be excluded. I haven't worked on implementing that yet. Let's continue to watch for feedback if people will desire this kind of control.

Using `exec git branch -f` is further discussed in the review, where there are arguments for introducing a new todo command. I'll add some comments there when I post a new patch set. But if someone's in favor of accepting a version of this without that change, with the potential harm from this feature being low enough, I'm not opposed to that either.

Previous: Taylor BlauNext: brian m. carlson
Message 13 of 16 in “rebase: introduce --update-branches option”
  1. rebase: introduce --update-branches optionWarren He, Sep 2, 2019
  2. rebase: introduce --update-branches optionWarren He, Sep 2, 2019
  3. Johannes SchindelinSep 3, 2019
  4. rebase: introduce --update-branches optionWarren He, Sep 7, 2019
  5. rebase: introduce --update-branches optionWarren He, Sep 7, 2019
  6. Phillip WoodSep 9, 2019
  7. Johannes SchindelinSep 9, 2019
  8. Junio C HamanoSep 9, 2019
  9. Phillip WoodSep 23, 2019
  10. brian m. carlsonSep 3, 2019
  11. Junio C HamanoSep 3, 2019
  12. Taylor BlauSep 3, 2019
  13. Warren HeSep 7, 2019
  14. brian m. carlsonSep 8, 2019
  15. Phillip WoodSep 3, 2019
  16. Warren HeSep 7, 2019

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.