| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Ancient cat-file command used to leave temp_git_file_* and there
was support to remove them in the clean target of Makefile. I
do not think it is needed anymore.
From: Junio C Hamano <junkio@cox.net>
Signed-off-by: Petr Baudis <pasky@ucw.cz>
|
|
|
|
|
|
|
|
|
| |
The nsec field of ctime/mtime is now checked only with -DNSEC defined during
compilation. nsec acts broken since it is stored in the icache but apparently
just gets to zero when flushed to filesystem not supporting it (e.g. ext3),
creating illusions of false changes. At least that's my impression.
Signed-off-by: Petr Baudis <pasky@ucw.cz>
|
|
|
|
|
|
|
|
| |
When compiled with -DCOLLISION_CHECK, we will check against SHA1
collisions when writing to the object database.
From: Christopher Li <chrislgit@chrisli.org>
Signed-off-by: Petr Baudis <pasky@ucw.cz>
|
|
|
|
|
|
|
|
|
|
| |
ls-tree tool provides just a way to export the binary tree objects
to a usable text format. This is bound to be useful in variety
of scripts, although none of those I have currently uses it.
But e.g. the simple script I've sent to HPA for purging the object
database uses it.
Signed-off-by: Petr Baudis <pasky@ucw.cz>
|
|
|
|
|
|
|
| |
patches.
In particular, it verifies that all the listed files are up-to-date
in the cache (or don't exist and are ready to be added).
|
|
|
|
| |
You want things like this to check in a patch..
|
|
|
|
|
|
|
|
| |
tree graph.
It's quite fast when the commit-objects are cached, but since
it has to walk every single commit-object, it also allows you
to cache an old state and just add on top of that.
|
|
|
|
|
| |
Very useful for creating diffs efficiently, and in general to see what has
changed in the namespace.
|
|
|
|
|
| |
I'll also eventually change "read-tree" to only update the cache
information, instead of doing a checkout of the tree. Much nicer.
|
|
|
|
|
| |
Not all Linux distributions seem to need it (notably not YDL on ppc64), but
enough ones obviously do.
|
|
|
|
|
| |
This is what happens when there are no nice tools to tell you to do things
properly.
|
|
|
|
|
|
|
| |
And fix up the warnings that it pointed out. Let's keep the tree
clean from early on.
Not that the code is very beautiful anyway ;)
|
|
|