| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
| |
This allows us to both calculate it and verify it faster.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
Do the usage and error reporting in "usage.c", and the sha1 file
accesses in "sha1_file.c".
Small, nice, easily separated parts. Good.
|
| |
|
|
|
|
|
|
|
| |
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).
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
| |
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.
|
| |
|
|
| |
This allows you to actually tell git that you've resolved a conflict.
|
| |
|
|
|
| |
This is what allows us to have multiple states of the same file in
the index, and what makes it always sort correctly.
|
| |
|
|
|
|
|
| |
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).
|
| |
|
|
|
|
| |
Not only did it test the #define the wrong way around, but
it also leaked file descriptors and VM space. This should
fix it.
|
| |
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
| |
I started out calling the tool "dircache". That's clearly moronic.
|
| |
|
|
| |
It got broken when I changed it to use stdarg.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
trees
as it diffs them.
This makes diff-tree usable again in the new world order.
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
| |
The "diff-tree" program needs it.
|
| |
|
|
|
|
| |
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).
|
| |
|
|
|
| |
Like the cache filename finder, it's a generically useful function,
rather than something specific to the current "show-diff" thing.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
And fix up header declarations.
|
| |
|
|
|
| |
This allows us to also actually check the sha1 hash using these
routines. Needed for the "fsck" thing.
|
| |
|
|
|
|
|
| |
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 ;)
|
| |
|
|
|
|
| |
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.
|
| |
|
