summaryrefslogtreecommitdiff
path: root/read-cache.c
AgeCommit message (Collapse)AuthorFilesLines
2005-04-26Allow writing to the private index file mapping.Libravatar Linus Torvalds1-1/+1
We now modify the in-memory copy of the index file in "diff-cache", so we need to add PROT_WRITE.
2005-04-26[PATCH] introduce xmalloc and xreallocLibravatar Christopher Li1-1/+1
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<chrislgit@chrisli.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-04-22New "diff-cache" implementation.Libravatar Linus Torvalds1-2/+2
This one is about a million times simpler, and much more likely to be correct too. Instead of trying to match up a tree object against the index, we just read in the tree object side-by-side into the index, and just walk the resulting index file. This was what all the read-tree cleanups were all getting to.
2005-04-21Add support for a "GIT_INDEX_FILE" environment variable.Libravatar Linus Torvalds1-1/+1
We use that to specify alternative index files, which can be useful if you want to (for example) generate a temporary index file to do some specific operation that you don't want to mess with your main one with. It defaults to the regular ".git/index" if it hasn't been specified.
2005-04-21Fix NSEC compile problem, and properly parse the rev-tree cmd line.Libravatar Linus Torvalds1-2/+2
The rev-tree thing just happened to work. It shouldn't have.
2005-04-20Make the sha1 of the index file go at the very end of the file.Libravatar Linus Torvalds1-23/+21
This allows us to both calculate it and verify it faster.
2005-04-20Speed up index file writing by chunking it nicely.Libravatar Linus Torvalds1-4/+39
No point in making 17,000 small writes when you can make just a couple of hundred nice 8kB writes instead and save a lot of time.
2005-04-18Split up read-cache.c into more logical clumps.Libravatar Linus Torvalds1-270/+0
Do the usage and error reporting in "usage.c", and the sha1 file accesses in "sha1_file.c". Small, nice, easily separated parts. Good.
2005-04-18[PATCH] fix bug in read-cache.c which loses files when merging a treeLibravatar James Bottomley1-1/+0
I noticed this when I tried a non-trivial scsi merge and checked the results against BK. The problem is that remove_entry_at() actually decrements active_nr, so decrementing it in add_cache_entry() before calling remove_entry_at() is a double decrement (hence we lose cache entries at the end).
2005-04-17[PATCH] Fix +x-related show-diff false positivesLibravatar Petr Baudis1-1/+1
This fixes show-diff listing all +x files as differring. Signed-off-by: Petr Baudis <pasky@ucw.cz> [ That's what I get for working on a G5 - my testing was all big-endian in the first place. -- Linus ] Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-04-17[PATCH] update-cache --remove marks the path merged.Libravatar Junio C Hamano1-1/+3
When update-cache --remove is run, resolve unmerged state for the path. This is consistent with the update-cache --add behaviour. Essentially, the user is telling us how he wants to resolve the merge by running update-cache. Signed-off-by: Junio C Hamano <junkio@cox.net> Fixed to do the right thing at the end. Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-04-16Be much more liberal about the file mode bits.Libravatar Linus Torvalds1-1/+2
We only really care about the difference between a file being executable or not (by its owner). Everything else we leave for the user umask to decide.
2005-04-16When inserting a index entry of stage 0, remove all old unmerged entries.Libravatar Linus Torvalds1-5/+31
This allows you to actually tell git that you've resolved a conflict.
2005-04-15Make cache entry comparison take the new "state" flag into account.Libravatar Linus Torvalds1-3/+9
This is what allows us to have multiple states of the same file in the index, and what makes it always sort correctly.
2005-04-15Convert the index file reading/writing to use network byte order.Libravatar Linus Torvalds1-27/+29
This allows using a git tree over NFS with different byte order, and makes it possible to just copy a fully populated repository and have the end result immediately usable (needing just a refresh to update the stat information).
2005-04-13Fix read-cache.c collission check logic.Libravatar Linus Torvalds1-11/+28
Not only did it test the #define the wrong way around, but it also leaked file descriptors and VM space. This should fix it.
2005-04-13[PATCH] Whitespace FixesLibravatar Ingo Molnar1-1/+1
Trivial whitespace fixes. From: Ingo Molnar <mingo@elte.hu> Signed-off-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Petr Baudis <pasky@ucw.cz>
2005-04-13[PATCH] Consolidate the error handlingLibravatar Petr Baudis1-14/+30
Now there is error() for "library" errors and die() for fatal "application" errors. usage() is now used strictly only for usage errors. Signed-off-by: Petr Baudis <pasky@ucw.cz>
2005-04-13[PATCH] Make nsec checking optionalLibravatar Petr Baudis1-4/+13
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>
2005-04-13[PATCH] SHA1 naive collision checkingLibravatar Petr Baudis1-2/+19
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>
2005-04-11Rename ".dircache" directory to ".git"Libravatar Linus Torvalds1-1/+1
I started out calling the tool "dircache". That's clearly moronic.
2005-04-11Fix "usage()" to do the missing line termination.Libravatar Linus Torvalds1-1/+3
It got broken when I changed it to use stdarg.
2005-04-10Fix off-by-one error in removal of cache entry.Libravatar Linus Torvalds1-7/+7
Also make the return value of "cache_name_pos()" be sane: positive or zero if we found it (it's the index into the cache array), and "-pos-1" to indicate where it should go if we didn't.
2005-04-10Add "-R" flag to "diff-tree", so that it will recursively traverse a tree of ↵Libravatar Linus Torvalds1-4/+4
trees as it diffs them. This makes diff-tree usable again in the new world order.
2005-04-10Make "update-cache" a bit friendlier to use (and harder to mis-use).Libravatar Linus Torvalds1-3/+10
It now requires the "--add" flag before you add any new files, and a "--remove" file if you want to mark files for removal. And giving it the "--refresh" flag makes it just update all the files that it already knows about.
2005-04-09This implements the new "recursive tree" write-tree.Libravatar Linus Torvalds1-2/+3
It's got some debugging printouts etc still in it, but testing on the kernel seems to show that it does indeed fix the issue with huge tree files for each commit.
2005-04-09Export "cache_name_compare()" helper function.Libravatar Linus Torvalds1-1/+1
The "diff-tree" program needs it.
2005-04-09Make "write_cache()" and friends available as generic routines.Libravatar Linus Torvalds1-2/+70
This is needed for the change to make "read-tree" just read into the cache (and then you do a "checkout-cache" to update your current dir contents).
2005-04-09Make the cache stat information comparator public.Libravatar Linus Torvalds1-0/+23
Like the cache filename finder, it's a generically useful function, rather than something specific to the current "show-diff" thing.
2005-04-09Make "cache_name_pos()" available to others.Libravatar Linus Torvalds1-0/+36
It finds the cache entry position for a given name, and is generally useful. Sure, everybody can just scan the active cache array, but since it's sorted, you actually want to search it with a binary search, so let's not duplicate that logic all over the place.
2005-04-09Fix missing return values and some error tests for empty index filesLibravatar Linus Torvalds1-2/+1
Patches from Dave Jones and Ingo Molnar, but since I don't have any infrastructure in place to use the old patch applicator scripts I am trying to build up, I ended up fixing the thing by hand instead. Credit where credit is due, though. Nice to see that people are taking a look at the project even in this early stage.
2005-04-08Add "check_sha1_signature()" helper functionLibravatar Linus Torvalds1-0/+11
And fix up header declarations.
2005-04-08Factor out "read_sha1_file" into mapping/inflating/unmapping.Libravatar Linus Torvalds1-9/+31
This allows us to also actually check the sha1 hash using these routines. Needed for the "fsck" thing.
2005-04-08Use "-Wall -O2" for the compiler to get more warnings.Libravatar Linus Torvalds1-2/+3
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 ;)
2005-04-07Add copyright notices.Libravatar Linus Torvalds1-0/+5
The tool interface sucks (especially "committing" information, which is just me doing everything by hand from the command line), but I think this is in theory actually a viable way of describing the world. So copyright it.
2005-04-07Initial revision of "git", the information manager from hellLibravatar Linus Torvalds1-0/+259