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

Re: [RFD] what should "git push remote.host:path" do?

From
Junio C Hamano <junkio@cox.net>
Date
Jan 12, 2006, 18:53 UTC
Message-ID
<7vbqyhp9ah.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.64.0601121006040.3535@g5.osdl.org>
Linus Torvalds <torvalds@osdl.org> writes:
> Well, especially if you want to use "git push" to basically back up your 
> own repo, you do want the "--all" flag. Otherwise you will then forget to 
> add a branch name to every remotes file whenyou create a new branch.

Sorry, I was unclear in my original message, but I meant to require at least one refspec to be given to the command. Ways to give refspec to the command are:

 (1) give one or more from the command line
 (2) give --all from the command line
 (3) give none from the command line, but in this case you need
     at least one "Push:" the "remotes" file you use.

We already have --all, but your "git push --tags $remote" makes sense. For backups, "only matching things" is not good enough, and we need --all.

Previous: Linus TorvaldsNext: Junio C Hamano
Message 6 of 7 in “[RFD] what should "git push remote.host:path" do?”
  1. Junio C HamanoJan 12, 2006
  2. SeanJan 12, 2006
  3. Junio C HamanoJan 12, 2006
  4. Nick HengeveldJan 12, 2006
  5. Linus TorvaldsJan 12, 2006
  6. Junio C HamanoJan 12, 2006
  7. git-push: avoid falling back on pushing "matching" refs.Junio C Hamano, Jan 13, 2006

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.