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

Re: Unhelpful "branch.master.remote = <nickname>" advice?

From
Jan Krüger <jk@jk.gs>
Date
Nov 11, 2009, 14:13 UTC
Message-ID
<20091111151338.3df1faa7@perceptron>
In-Reply-To
<1257945756.26362.79.camel@heerbeest>
Hi,
Show 7 quoted lines
> git pull -r*) URL says: [...]
>         branch.master.remote = <nickname>
> and after cut-and-pasting that into .git/config, replacing
> <foo> with values, I get [...]
>     fatal: bad config file line 17 in .git/config
> where line 17 is [without any indentation]
>     branch.master.remote = eddy

The confusion is that while you can set values with this syntax if you're using git config (git config branch.master.remote <some value>), they're written differently in actual config files:

  [branch "master"]
  remote = <nickname>
  merge = <remote-ref>
  
  [remote "<nickname>"]
  url = <url>
  fetch = <refspec>

I can't think of a message of comparable length that would make this clearer, though.

> Jan.  -- who just finds out the uninstall target is missing?!?
> 	 See attached.

I have no comments about the patch contents themselves, but please read Documentation/SubmittingPatches. Most importantly, patches are usually sent inline here, and without a signoff line they can't be accepted for inclusion in the official repository.

> *) I've been wondering why GIT lacks a "update", ie
>    pull-without-merge command.  You almost never want
>    to git pull /without/ -r?

-r stands for "rebase", i.e. it makes git pull use rebase instead of merge. Rebase has certain problematic implications for decentralized development, which is why it should only really be used in specific circumstances (for rebasing commits that haven't been published in any way yet).

"You" may almost never want to use git pull without rebase, but "many others" do, and very often. Personally, I donn't recall a single occasion where I have used git pull --rebase (not counting git-svn stuff).

Anyway, look at config options branch.autosetuprebase and branch.<nickname>.rebase to see how you can make pull use rebase by default.

-Jan
Previous: Matthieu MoyNext: Junio C Hamano
Message 5 of 26 in “Unhelpful "branch.master.remote = <nickname>" advice?”
  1. Jan NieuwenhuizenNov 11, 2009
  2. Tomas CarneckyNov 11, 2009
  3. Makefile: add uninstall target. Fixes elementary good cleaning manners.Jan Nieuwenhuizen, Nov 18, 2009
  4. Matthieu MoyNov 18, 2009
  5. Jan KrügerNov 11, 2009
  6. Junio C HamanoNov 11, 2009
  7. Tomas CarneckyNov 11, 2009
  8. Jan NieuwenhuizenNov 11, 2009
  9. Tomas CarneckyNov 11, 2009
  10. Jan NieuwenhuizenNov 12, 2009
  11. git-pull.sh: overhaul error handling when no candidates are foundJan Krüger, Nov 12, 2009
  12. Jeff KingNov 12, 2009
  13. Jan KrügerNov 12, 2009
  14. Jeff KingNov 12, 2009
  15. git-pull.sh --rebase: overhaul error handling when no candidates are foundJan Krüger, Nov 12, 2009
  16. Jonathan NiederNov 13, 2009
  17. pull: clarify advice for the unconfigured error caseJonathan Nieder, Nov 27, 2009
  18. Junio C HamanoDec 2, 2009
  19. Jonathan NiederDec 3, 2009
  20. Jeff KingDec 3, 2009
  21. Jan NieuwenhuizenDec 3, 2009
  22. Jan KrügerDec 3, 2009
  23. Junio C HamanoDec 7, 2009
  24. Junio C HamanoNov 15, 2009
  25. Björn SteinbrinkNov 12, 2009
  26. Tomas CarneckyNov 12, 2009

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.