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

[DOC BUG] branch.autosetupmerge defaults to true, not false

From
KNKalle Olavi Niemitalo <kon@iki.fi>
Date
Feb 11, 2008, 08:46 UTC
Message-ID
<87bq6nc22l.fsf@Astalo.kon.iki.fi>
In Git v1.5.4.1, Documentation/config.txt describes:
Show 6 quoted lines
> branch.autosetupmerge::
>         Tells `git-branch` and `git-checkout` to setup new branches
>         so that linkgit:git-pull[1] will appropriately merge from that
>         remote branch.  Note that even if this option is not set,
>         this behavior can be chosen per-branch using the `--track`
>         and `--no-track` options.  This option defaults to false.
However, in builtin-branch.c:
> static int branch_track = 1;
...
>         if (!strcmp(var, "branch.autosetupmerge"))
>                         branch_track = git_config_bool(var, value);

So if the option is not listed in .git/config, then it actually defaults to true. A demonstration with a bit older version:

$ git --version git version 1.5.4.rc3 $ git config --unset branch.autosetupmerge $ git branch demo elinks.cz/master Branch demo set up to track remote branch refs/remotes/elinks.cz/master. $

Next: Junio C Hamano
Message 1 of 4 in “[DOC BUG] branch.autosetupmerge defaults to true, not false”
  1. Kalle Olavi NiemitaloFeb 11, 2008
  2. Junio C HamanoFeb 11, 2008
  3. Johannes SchindelinFeb 11, 2008
  4. Johannes SchindelinFeb 11, 2008

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.