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

Update local tracking refs when pushing- no way to disable

From
Dan McGee <dpmcgee@gmail.com>
Date
Jul 6, 2007, 00:22 UTC
Message-ID
<449c10960707051722q6650ec7dq6012695acdfba4af@mail.gmail.com>

In this commit: b516968ff62ec153e008d033c153affd7ba9ddc6

I don't know if anyone else has the same way of working as I do, but I tend to set the "remote.<name>.skipDefaultUpdate" property to true for my publicly visible repository, just so I don't have duplicate branch heads lying around in my local repository. Call this peculiar, but I like it that way. However, git-push does not respect this property, meaning I know have these branches whether I want them or not. In a tool such as qgit or even 'git branch -a' output, it starts to get awful cluttered.

I'm not terribly familiar with GIT internals, so I don't know that I am the best to make a patch for this, but I'll take no response as a answer that I should start coding something up. Please CC me on emails, I'm not on the GIT mailing list.

-Dan
Next: Johannes Schindelin
Message 1 of 12 in “Update local tracking refs when pushing- no way to disable”
  1. Dan McGeeJul 6, 2007
  2. Johannes SchindelinJul 6, 2007
  3. Junio C HamanoJul 6, 2007
  4. Daniel BarkalowJul 6, 2007
  5. Marco CostalbaJul 6, 2007
  6. Shawn O. PearceJul 6, 2007
  7. Johannes SchindelinJul 6, 2007
  8. Daniel BarkalowJul 6, 2007
  9. Johannes SchindelinJul 6, 2007
  10. Daniel BarkalowJul 6, 2007
  11. Johannes SchindelinJul 6, 2007
  12. Dan McGeeJul 6, 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.