From: A Large Angry SCM <gitzilla@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Notes on supporting Git operations in/on partial Working Directories
Date: Thu, 14 Sep 2006 13:19:32 -0700 [thread overview]
Message-ID: <4509B954.60101@gmail.com> (raw)
In-Reply-To: <7vu03a2po8.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> A Large Angry SCM <gitzilla@gmail.com> writes:
...
>
> While this may be a good start, you need a lot more than this if
> you want to do (1) and (2):
>
> The tree object contained by a commit is by definition a full
> tree snapshot, so if you want to do a WD_Prefix, you somehow
> need a way to come up with the final tree that is a combination
> of what write-tree would write out from such a partial index
> (i.e. an index that describes only a subdirectory) and the rest
> of the tree from the current HEAD. I think you can more or less
> do this change to Porcelain using today's git core. The
> sequence to emulate it with the today's git would be:
I think you misunderstood, the index file would list all of the tree
entries of the the checked out commit, same as the current index, but
would flag the entries that are actually present in the working
directory. The WD_Prefix is to identify which index entries _can not_ be
part of the working directory, and where the working directory fits in
the full index. That way, all the information needed by the top level
write-tree is still in the index and the cache-tree extension.
next prev parent reply other threads:[~2006-09-14 20:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 19:05 Notes on supporting Git operations in/on partial Working Directories A Large Angry SCM
2006-09-14 19:21 ` Shawn Pearce
2006-09-14 20:08 ` A Large Angry SCM
2006-09-14 19:50 ` Junio C Hamano
2006-09-14 20:19 ` A Large Angry SCM [this message]
2006-09-15 2:43 ` Junio C Hamano
2006-09-15 18:15 ` A Large Angry SCM
2006-09-17 10:43 ` Junio C Hamano
2006-09-17 18:47 ` A Large Angry SCM
2006-09-17 18:55 ` Jakub Narebski
2006-09-17 20:01 ` A Large Angry SCM
2006-09-17 20:28 ` Jakub Narebski
2006-09-17 21:11 ` A Large Angry SCM
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=4509B954.60101@gmail.com \
--to=gitzilla@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).