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

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

From
Tomas Carnecky <tom@dbservice.com>
Date
Nov 11, 2009, 14:08 UTC
Message-ID
<48B54636-1825-48B3-BECD-4150A55B013F@dbservice.com>
In-Reply-To
<1257945756.26362.79.camel@heerbeest>
On Nov 11, 2009, at 2:22 PM, Jan Nieuwenhuizen wrote:
Show 12 quoted lines
> Hi,
>
> git pull -r*) URL says:
>
>    If you often merge with the same branch, you may want to
>    configure the following variables in your configuration
>    file:
>
>        branch.master.remote = <nickname>
>        branch.master.merge = <remote-ref>
>        remote.<nickname>.url = <url>
>        remote.<nickname>.fetch = <refspec>

These are meant to be used with git-config(1): git config branch.master.remote <nickname>

Or if you want to manually edit the config file, add this:
[branch "master"]
     remote = <nickname>
etc.
Show 16 quoted lines
>
> and after cut-and-pasting that into .git/config, replacing
> <foo> with values, I get
>
>    $ git pull -r http://github.com/../../master
>    fatal: bad config file line 17 in .git/config
>
> where line 17 is [without any indentation]
>
>    branch.master.remote = eddy
>
> This is with git version version 1.6.3.3
>
> Greetings,
> Jan.  -- who just finds out the uninstall target is missing?!?
> 	 See attached.

Next time please send patches inline, it's easier to review them that way.

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

As 'pull == fetch + merge' (pull -r == fetch + rebase), pull without merge would be fetch.

tom
Previous: Jan NieuwenhuizenNext: Jan Nieuwenhuizen
Message 2 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.