Re: Problem creating commits/trees with commit-tree/mktree
- From
Avery Pennarun <apenwarr@gmail.com>
- Date
- Jan 11, 2010, 18:38 UTC
- Message-ID
- <32541b131001111038m3dacaf72sc12f24aba8c60e@mail.gmail.com>
- In-Reply-To
- <f6d77fed1001111014g73a06923na05cd14d37968b04@mail.gmail.com>
On Mon, Jan 11, 2010 at 1:14 PM, Gavin Beatty <gavinbeatty@gmail.com> wrote:
> I can create new blobs and trees but can't figure out how to commit a > new tree/blob _with_ the old tree.
[...]
> I get a commit with treefileisin/file.txt. I haven't included the > other trees/files so they are gone in this commit. How do I include > them? Is commit-tree the wrong tool?
When I'm doing similar things, I often prefer just using a temporary git index file to keep track of my intermediate trees. Just set GIT_INDEX_FILE to point at a temporary file; then you can use git-read-tree to read in an old tree, and git-update-index (particularly with the --stdin flag) to update it. Then you can use git-write-tree to convert the temporary index into a real tree object.
Have fun,
Avery