From: Timothy Shimmin <tes@sgi.com>
To: Shawn Pearce <spearce@spearce.org>
Cc: git <git@vger.kernel.org>
Subject: Re: git pull a subtree, embedded trees
Date: Mon, 18 Sep 2006 15:57:12 +1000 [thread overview]
Message-ID: <450E3538.4010209@sgi.com> (raw)
In-Reply-To: <20060913150028.GB29608@spearce.org>
Hi Shawn,
Shawn Pearce wrote:
> Tim Shimmin <tes@sgi.com> wrote:
>> I've written a simple small program to dump out the index
>> entries (cache entries).
>
> `git-ls-files --stage` also dumps a number of those details, though
> it doesn't dump every available field.
>
Thanks, that's handy.
However, when going through the core-tutorial (copying repository section)
and populating the index from the .git objects using git-read-tree,
it was nice to see all the stat fields using my program.
These fields were empty at that stage, of course, (it was nice to see it)
until I had populated the workarea using git-checkout-index.
But generally, git-ls-files --stage would be fine.
>> I just want to see what is exactly stored in the .git
>> binary files and how they change when I do various git
>> operations.
>
> You may want to review some of the material in
> Documentation/core-tutorial.txt and Documentation/technical.
> These documents try to describe some of the formats but reviewing
> them now it looks like there's still some additional information
> that could be written down.
>
Thanks. I've been going through the core-tutorial.
It's great.
Cheers,
Tim.
prev parent reply other threads:[~2006-09-18 5:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 13:05 git pull a subtree, embedded trees Tim Shimmin
2006-09-13 14:21 ` Jakub Narebski
2006-09-18 5:50 ` Timothy Shimmin
2006-09-18 5:58 ` Jakub Narebski
2006-09-18 6:42 ` Shawn Pearce
2006-09-18 6:47 ` Shawn Pearce
2006-09-13 15:00 ` Shawn Pearce
2006-09-18 5:57 ` Timothy Shimmin [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=450E3538.4010209@sgi.com \
--to=tes@sgi.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).