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

Re: git push in --tracked branches.

From
AAghiles <aghilesk@gmail.com>
Date
Apr 22, 2010, 01:13 UTC
Message-ID
<i2n3abd05a91004211813t8111c77am381bc0b8226a0c9b@mail.gmail.com>
In-Reply-To
<20100422004433.GC14249@coredump.intra.peff.net>
On Wed, Apr 21, 2010, Jeff King <peff@peff.net> wrote:
> "git push" will by default push matching refs. This has been the
> behavior since day one. See the description of push.default in "git help
> config" for other options (I think you want "tracking").

Thank you very much. The 'tracking' case is what I need. Could you enlighten me why pushing all matching branches is a sensible default ? It seems like an unusual thing to do.

  -- aghiles
Previous: Jeff KingNext: Jeff King
Message 3 of 5 in “git push in --tracked branches.”
  1. AghilesApr 22, 2010
  2. Jeff KingApr 22, 2010
  3. AghilesApr 22, 2010
  4. Jeff KingApr 22, 2010
  5. AghilesApr 22, 2010

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.