From: "Aneesh Kumar" <aneesh.kumar@gmail.com>
To: "Petr Baudis" <pasky@suse.cz>
Cc: "Junio C Hamano" <junkio@cox.net>, git@vger.kernel.org
Subject: Re: simple use case scenario for --read-tree and --write-tree with --prefix option
Date: Mon, 19 Jun 2006 21:20:08 +0530 [thread overview]
Message-ID: <cc723f590606190850q4a200423ve3304c4f7df20267@mail.gmail.com> (raw)
In-Reply-To: <20060619135343.GP2609@pasky.or.cz>
On 6/19/06, Petr Baudis <pasky@suse.cz> wrote:
> Dear diary, on Mon, Jun 19, 2006 at 09:58:31AM CEST, I got a letter
> where Aneesh Kumar <aneesh.kumar@gmail.com> said that...
> > 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.
>
> You need to do a fetch to your /tmp/test repository first.
>
Ok that made the --read-tree part work. But the log or whatchanged
commands doesn't gets me the history of changes with resepect to the
files added. Now i remember this is in a way simillar to gitweb
history not shown. But then using the --full-history option with git
log also doesn't show the details of history with respect to the
files.
This is what i did
git fetch ./test2/
git read-tree --prefix=test2/ $(cat test2/.git/refs/heads/master)
Now if i look at .git/objects/ I can see commit objects with respect
to changes for test2/a
-aneesh
prev parent reply other threads:[~2006-06-19 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 7:28 simple use case scenario for --read-tree and --write-tree with --prefix option Aneesh Kumar
2006-06-19 7:52 ` Junio C Hamano
2006-06-19 7:58 ` Aneesh Kumar
2006-06-19 13:53 ` Petr Baudis
2006-06-19 15:50 ` Aneesh Kumar [this message]
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=cc723f590606190850q4a200423ve3304c4f7df20267@mail.gmail.com \
--to=aneesh.kumar@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pasky@suse.cz \
/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).