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

Correct way to pull using subtree merge without guesswork?

From
MRManuel Reimer <manuel.spam@nurfuerspam.de>
Date
Jan 24, 2012, 17:49 UTC
Message-ID
<jfmr88$1p8$1@dough.gmane.org>
Hello,

can someone please tell me, if this is the correct syntax for using "git pull" to pull in "subtree merging strategy", if I don't want to allow git to guess where to do the changes:

git pull -s subtree -X subtree=path/to/subtree externalproject master

Returns with success, but is "-X subtree=" the right way to force a subtree path and disallow git to autodetect the subtree?

$ git --version git version 1.7.4.4

Thank you very much in advance
Yours
Manuel
Next: Junio C Hamano
Message 1 of 2 in “Correct way to pull using subtree merge without guesswork?”
  1. Manuel ReimerJan 24, 2012
  2. Junio C HamanoJan 24, 2012

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.