From: SungHyun Nam <namsh@posdata.co.kr>
To: git@vger.kernel.org
Subject: Re: using merge subtree and move it..
Date: Tue, 09 Sep 2008 18:59:45 +0900 [thread overview]
Message-ID: <48C64911.4020202@posdata.co.kr> (raw)
In-Reply-To: <48C61E1F.6000907@viscovery.net>
Johannes Sixt wrote:
> SungHyun Nam schrieb:
>> I used the subtree merge strategy. And then I moved the directory.
>> Now, can I use subtree merge for that new directory?
>
> Sure. It should work just fine.
>
>> $ git pull -s subtree klib master
>> remote: Counting objects: 5, done.
>> remote: Compressing objects: 100% (2/2), done.
>> remote: Total 3 (delta 1), reused 0 (delta 0)
>> Unpacking objects: 100% (3/3), done.
>> From ssh://192.168.10.10/git/libs/klib
>> * branch master -> FETCH_HEAD
>> error: Entry 'klib/klib.c' not uptodate. Cannot merge.
>
> Your problem is not related to subtree merge. Make sure you have no
> changes to commit before you merge.
It seems I forgot to commit after running 'git mv lib/klib klib'.
Oops! :( I'm not sure because the problem gone after I did some
stupid things. The 'some stupid things' include 'git rm -rf klib;
...; git remote rm klib and re-doing using-merge-subtree.....'.
BTW, I have no idea how I can push 'local changes in subtree' to remote.
The 'Additional tips' in using-merge-subtree.txt said it is
possible using subtree. But don't know how? Could someone show me
a sample command/setup sequence?
Thanks,
namsh
next prev parent reply other threads:[~2008-09-09 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 0:21 using merge subtree and move it SungHyun Nam
2008-09-09 6:56 ` Johannes Sixt
2008-09-09 9:59 ` SungHyun Nam [this message]
2009-11-03 2:57 ` Milos Jakubicek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48C64911.4020202@posdata.co.kr \
--to=namsh@posdata.co.kr \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.