git/write-tree.c, branch v1.2.2

write-tree: check extra arguments and die but be a bit more helpful.

2005-12-06T06:31:18Z

"git-write-tree junk" complains and dies, but it does not say what option it supports. Die with the usage string in such a case. Signed-off-by: Junio C Hamano

Make the rest of commands work from a subdirectory.

2005-11-29T07:13:02Z

These commands are converted to run from a subdirectory. commit-tree convert-objects merge-base merge-index mktag pack-objects pack-redundant prune-packed read-tree tar-tree unpack-file unpack-objects update-server-info write-tree Signed-off-by: Junio C Hamano

[PATCH] Trivial tidyups

2005-07-30T00:21:49Z

Simple whitespace-related tidyups ensuring style consistency. This is carried over from my old git-pb branch. Signed-off-by: Petr Baudis Signed-off-by: Junio C Hamano

[PATCH] add --missing-ok option to write-tree

2005-07-11T17:20:53Z

This option allows a write-tree even if the referenced objects are not in the database. Signed-off-by: Bryan Larsen Signed-off-by: Linus Torvalds

[PATCH] git-write-tree doesn't check alternate directories

2005-06-25T20:41:10Z

git-write-tree failed when referenced objects only exist in the GIT_ALTERNATE_OBJECT_DIRECTORIES path. Signed-off-by: Jan Harkes Acked-by: Junio C Hamano Signed-off-by: Linus Torvalds

[PATCH] cleanup of in-code names

2005-05-19T17:52:00Z

Fixes all in-code names that leaved during "big name change". Signed-off-by: Alexey Nezhdanov Signed-off-by: Linus Torvalds

Merge with http://members.cox.net/junkio/git-jc.git

2005-05-11T00:00:49Z

write-tree is now willing to write empty tree

2005-05-08T14:15:59Z

Cogito wants to be able to do some initial commit at the time of cg-init, which may be empty in case when cg-init is called in an empty tree.

Notice index that has path and path/file and refuse to write such a tree.

2005-05-07T19:22:02Z

Kay Sievers noticed that you can have both path and path/file in the cache and write-tree happily creates a tree object from such a state. Since a merge can result in such situation and the user should be able to see the situation by looking at the cache, rather than forbidding add_cache_entry() to create such conflicts, fix it by making write-tree refuse to write such an nonsensical tree. Here is a test case. -- test case -- $ ls -a ./ ../ $ git-init-db defaulting to local storage area $ date >path $ git-update-cache --add path $ rm path $ mkdir path $ date >path/file $ git-update-cache --add path/file $ git-ls-files --stage 100644 1738f2536b1201218c41153941da065cc26174c9 0 path 100644 620c72f1c1de15f56ff9d63d6d7cdc69e828f1e3 0 path/file $ git-ls-tree $(git-write-tree) ;# using old one 100644 blob 1738f2536b1201218c41153941da065cc26174c9 path 040000 tree ec116937f223e3df95aeac9f076902ae1618ae98 path $ ../git-write-tree ;# using new one You have both path and path/file fatal: write-tree: not able to write tree $ exit Signed-off-by: Junio C Hamano

[PATCH] introduce xmalloc and xrealloc

2005-04-26T19:00:58Z

Introduce xmalloc and xrealloc to die gracefully with a descriptive message when out of memory, rather than taking a SIGSEGV. Signed-off-by: Christopher Li Signed-off-by: Linus Torvalds