Re: simple use case scenario for --read-tree and --write-tree with --prefix option

From: Aneesh Kumar <aneesh.kumar@gmail.com>
Date: Jun 19, 2006, 07:58 UTC
Message-ID: <cc723f590606190058w2d7481ecsaded46095aee2355@mail.gmail.com>
In-Reply-To: <7vpsh5a8gs.fsf@assigned-by-dhcp.cox.net>

On 6/19/06, Junio C Hamano <junkio@cox.net> wrote:

Show 11 quoted lines

> "Aneesh Kumar" <aneesh.kumar@gmail.com> writes:
>
> > I searched the archives but didn't find anything. If i understand
> > correctly the sub project idea is using the gitlink object type. So
> > what is read-tree and write-tree with --prefix option supposed to
> > achieve.
>
> The --prefix option to read-tree was very useful when I did a
> hand merge of gitweb for example.  I am reasonably sure clever
> people will find other uses as well.
>

Ok i tried this mkdir test/test1 mkdir test/test2 cd test git init-db cd test1 git init-db cd ../test2 git init-db

now i do some devel under test2 now if i want to pull this with the history to toplevel directory test should i be doing

cd test

kvaneesh@satan:/tmp/test$ git read-tree --prefix=test1/ $(cat test1/.git/refs/heads/master) fatal: failed to unpack tree object c6c049d03f0bee0ac546ff6e436d5f6f3a5f4864

But the above command doesn't work for me. I guess i am missing something.

-aneesh