* Correct way to pull using subtree merge without guesswork?
@ 2012-01-24 17:49 Manuel Reimer
2012-01-24 18:27 ` Junio C Hamano
0 siblings, 1 reply; 2+ messages in thread
From: Manuel Reimer @ 2012-01-24 17:49 UTC (permalink / raw)
To: git
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Correct way to pull using subtree merge without guesswork?
2012-01-24 17:49 Correct way to pull using subtree merge without guesswork? Manuel Reimer
@ 2012-01-24 18:27 ` Junio C Hamano
0 siblings, 0 replies; 2+ messages in thread
From: Junio C Hamano @ 2012-01-24 18:27 UTC (permalink / raw)
To: Manuel Reimer; +Cc: git
Manuel Reimer <Manuel.Spam@nurfuerspam.de> writes:
> 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?
More or less. Note that with the syntax, you cannot still express the
distinction between mapping the root of external to path/to/subtree of
your current tree and mapping the other way around, but that is not an
issue in practice.
By the way, I had an impression that "-X subtree" makes "-s subtree"
redundant and unnecessary.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-01-24 18:27 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-01-24 17:49 Correct way to pull using subtree merge without guesswork? Manuel Reimer
2012-01-24 18:27 ` Junio C Hamano
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox