git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* read-tree bug
@ 2014-05-06 12:35 Klishevich, Yauheni
  2014-05-06 13:32 ` Klishevich, Yauheni
  0 siblings, 1 reply; 2+ messages in thread
From: Klishevich, Yauheni @ 2014-05-06 12:35 UTC (permalink / raw)
  To: git@vger.kernel.org

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-05-06 16:42 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-05-06 12:35 read-tree bug Klishevich, Yauheni
2014-05-06 13:32 ` Klishevich, Yauheni

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).