From: "Klishevich, Yauheni" <yklishevich@scnsoft.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: read-tree bug
Date: Tue, 6 May 2014 12:35:27 +0000 [thread overview]
Message-ID: <CF8EB1C1.996%yklishevich@scnsoft.com> (raw)
Hello!
I have some troubles with git command ³read-tree².
I have big project and I try to add shared library to subdirectory. So I
made the following in my project (on master)
git remote add git@bitbucket.org:ijin1984/groundwork.git
git fetch groundwork
git checkout b gwbranch groundwork/master
git checkout master
git read-tree --prefix=mb/trunk/src/ru.uralsib.dbo.client.iphone/libs/ -u
gwbranch
git commit m ³add groundwork to libs²
After that I make small change in one file inside libs (for example in
"mb/trunk/src/ru.uralsib.dbo.client.iphone/libs/groundwork/notes.txt² and
commit with
git commit a m ³test commit²
Then I made:
git checkout gwbranch
git merge --squash -s subtree --no-commit master
And after this instead of merging I find the whole main project in subdir
³groundwork/Groundwork/Base.lproj².
If I do the 5-th command with ‹prefix option value equal to for example
³libs² tether than something like ³subdir/subsubdir/Š/libs² - all works
fine.
I think that it is bag, because I experimented quite a lot with deferrent
values. I think that problem in directory name with dots, i.e.
"ru.uralsib.dbo.client.iphone².
Could you please help me with this issue. If you need to add some more
info about this case I will provide.
Thanks in advance.
Best regards,
Eugene Klishevich
iOS-developer
skype: eugene.klishevich
next reply other threads:[~2014-05-06 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 12:35 Klishevich, Yauheni [this message]
2014-05-06 13:32 ` read-tree bug Klishevich, Yauheni
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=CF8EB1C1.996%yklishevich@scnsoft.com \
--to=yklishevich@scnsoft.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).