|
|
|
# -DCOLLISION_CHECK if you believe that SHA1's
|
|
|
|
# 1461501637330902918203684832716283019655932542976 hashes do not give you
|
|
|
|
# enough guarantees about no collisions between objects ever hapenning.
|
|
|
|
#
|
|
|
|
# -DUSE_NSEC if you want git to care about sub-second file mtimes and ctimes.
|
|
|
|
# -DUSE_STDEV if you want git to care about st_dev changing
|
|
|
|
#
|
|
|
|
# Note that you need some new glibc (at least >2.2.4) for this, and it will
|
|
|
|
# BREAK YOUR LOCAL DIFFS! show-diff and anything using it will likely randomly
|
|
|
|
# break unless your underlying filesystem supports those sub-second times
|
|
|
|
# (my ext3 doesn't).
|
|
|
|
GIT_VERSION=0.99.1
|
|
|
|
|
|
|
|
COPTS=-O2
|
|
|
|
CFLAGS=-g $(COPTS) -Wall
|
|
|
|
|
|
|
|
prefix=$(HOME)
|
|
|
|
bin=$(prefix)/bin
|
|
|
|
# dest=
|
|
|
|
|
|
|
|
CC=gcc
|
|
|
|
AR=ar
|
|
|
|
INSTALL=install
|
|
|
|
RPMBUILD=rpmbuild
|
|
|
|
|
|
|
|
#
|
|
|
|
# sparse is architecture-neutral, which means that we need to tell it
|
|
|
|
# explicitly what architecture to check for. Fix this up for yours..
|
|
|
|
#
|
|
|
|
SPARSE_FLAGS=-D__BIG_ENDIAN__ -D__powerpc__
|
|
|
|
|
|
|
|
SCRIPTS=git git-apply-patch-script git-merge-one-file-script git-prune-script \
|
|
|
|
git-pull-script git-tag-script git-resolve-script git-whatchanged \
|
|
|
|
git-fetch-script git-status-script git-commit-script \
|
|
|
|
git-log-script git-shortlog git-cvsimport-script git-diff-script \
|
|
|
|
git-reset-script git-add-script git-checkout-script git-clone-script \
|
|
|
|
gitk git-cherry git-rebase-script git-relink-script git-repack-script \
|
|
|
|
git-format-patch-script git-sh-setup-script git-push-script \
|
|
|
|
git-branch-script git-parse-remote git-verify-tag-script \
|
|
|
|
git-ls-remote-script git-clone-dumb-http
|
|
|
|
|
|
|
|
PROG= git-update-cache git-diff-files git-init-db git-write-tree \
|
|
|
|
git-read-tree git-commit-tree git-cat-file git-fsck-cache \
|
|
|
|
git-checkout-cache git-diff-tree git-rev-tree git-ls-files \
|
|
|
|
git-check-files git-ls-tree git-merge-base git-merge-cache \
|
|
|
|
git-unpack-file git-export git-diff-cache git-convert-cache \
|
|
|
|
git-http-pull git-ssh-push git-ssh-pull git-rev-list git-mktag \
|
|
|
|
git-diff-helper git-tar-tree git-local-pull git-hash-object \
|
|
|
|
git-get-tar-commit-id git-apply git-stripspace \
|
|
|
|
git-diff-stages git-rev-parse git-patch-id git-pack-objects \
|
|
|
|
git-unpack-objects git-verify-pack git-receive-pack git-send-pack \
|
|
|
|
git-prune-packed git-fetch-pack git-upload-pack git-clone-pack \
|
[PATCH] Add update-server-info.
The git-update-server-info command prepares informational files
to help clients discover the contents of a repository, and pull
from it via a dumb transport protocols. Currently, the
following files are produced.
- The $repo/info/refs file lists the name of heads and tags
available in the $repo/refs/ directory, along with their
SHA1. This can be used by git-ls-remote command running on
the client side.
- The $repo/info/rev-cache file describes the commit ancestry
reachable from references in the $repo/refs/ directory. This
file is in an append-only binary format to make the server
side friendly to rsync mirroring scheme, and can be read by
git-show-rev-cache command.
- The $repo/objects/info/pack file lists the name of the packs
available, the interdependencies among them, and the head
commits and tags contained in them. Along with the other two
files, this is designed to help clients to make smart pull
decisions.
The git-receive-pack command is changed to invoke it at the end,
so just after a push to a public repository finishes via "git
push", the server info is automatically updated.
In addition, building of the rev-cache file can be done by a
standalone git-build-rev-cache command separately.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
20 years ago
|
|
|
git-show-index git-daemon git-var git-peek-remote \
|
|
|
|
git-update-server-info git-show-rev-cache git-build-rev-cache
|
|
|
|
|
|
|
|
all: $(PROG)
|
|
|
|
|
|
|
|
install: $(PROG) $(SCRIPTS)
|
|
|
|
$(INSTALL) -m755 -d $(dest)$(bin)
|
|
|
|
$(INSTALL) $(PROG) $(SCRIPTS) $(dest)$(bin)
|
|
|
|
|
|
|
|
LIB_OBJS=read-cache.o sha1_file.o usage.o object.o commit.o tree.o blob.o \
|
|
|
|
tag.o date.o index.o diff-delta.o patch-delta.o entry.o path.o \
|
|
|
|
epoch.o refs.o csum-file.o pack-check.o pkt-line.o connect.o ident.o
|
|
|
|
LIB_FILE=libgit.a
|
|
|
|
LIB_H=cache.h object.h blob.h tree.h commit.h tag.h delta.h epoch.h csum-file.h \
|
|
|
|
pack.h pkt-line.h refs.h
|
|
|
|
|
[PATCH] Add update-server-info.
The git-update-server-info command prepares informational files
to help clients discover the contents of a repository, and pull
from it via a dumb transport protocols. Currently, the
following files are produced.
- The $repo/info/refs file lists the name of heads and tags
available in the $repo/refs/ directory, along with their
SHA1. This can be used by git-ls-remote command running on
the client side.
- The $repo/info/rev-cache file describes the commit ancestry
reachable from references in the $repo/refs/ directory. This
file is in an append-only binary format to make the server
side friendly to rsync mirroring scheme, and can be read by
git-show-rev-cache command.
- The $repo/objects/info/pack file lists the name of the packs
available, the interdependencies among them, and the head
commits and tags contained in them. Along with the other two
files, this is designed to help clients to make smart pull
decisions.
The git-receive-pack command is changed to invoke it at the end,
so just after a push to a public repository finishes via "git
push", the server info is automatically updated.
In addition, building of the rev-cache file can be done by a
standalone git-build-rev-cache command separately.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
20 years ago
|
|
|
LIB_H += rev-cache.h
|
|
|
|
LIB_OBJS += rev-cache.o
|
|
|
|
|
|
|
|
LIB_H += strbuf.h
|
|
|
|
LIB_OBJS += strbuf.o
|
|
|
|
|
|
|
|
LIB_H += quote.h
|
|
|
|
LIB_OBJS += quote.o
|
|
|
|
|
|
|
|
LIB_H += diff.h count-delta.h
|
|
|
|
LIB_OBJS += diff.o diffcore-rename.o diffcore-pickaxe.o diffcore-pathspec.o \
|
|
|
|
count-delta.o diffcore-break.o diffcore-order.o
|
|
|
|
|
|
|
|
LIB_OBJS += gitenv.o
|
[PATCH] Add update-server-info.
The git-update-server-info command prepares informational files
to help clients discover the contents of a repository, and pull
from it via a dumb transport protocols. Currently, the
following files are produced.
- The $repo/info/refs file lists the name of heads and tags
available in the $repo/refs/ directory, along with their
SHA1. This can be used by git-ls-remote command running on
the client side.
- The $repo/info/rev-cache file describes the commit ancestry
reachable from references in the $repo/refs/ directory. This
file is in an append-only binary format to make the server
side friendly to rsync mirroring scheme, and can be read by
git-show-rev-cache command.
- The $repo/objects/info/pack file lists the name of the packs
available, the interdependencies among them, and the head
commits and tags contained in them. Along with the other two
files, this is designed to help clients to make smart pull
decisions.
The git-receive-pack command is changed to invoke it at the end,
so just after a push to a public repository finishes via "git
push", the server info is automatically updated.
In addition, building of the rev-cache file can be done by a
standalone git-build-rev-cache command separately.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
20 years ago
|
|
|
LIB_OBJS += server-info.o
|
|
|
|
|
|
|
|
LIBS = $(LIB_FILE)
|
|
|
|
LIBS += -lz
|
|
|
|
|
|
|
|
ifdef MOZILLA_SHA1
|
|
|
|
SHA1_HEADER="mozilla-sha1/sha1.h"
|
|
|
|
LIB_OBJS += mozilla-sha1/sha1.o
|
|
|
|
else
|
|
|
|
ifdef PPC_SHA1
|
|
|
|
SHA1_HEADER="ppc/sha1.h"
|
|
|
|
LIB_OBJS += ppc/sha1.o ppc/sha1ppc.o
|
|
|
|
else
|
|
|
|
SHA1_HEADER=<openssl/sha.h>
|
|
|
|
LIBS += -lcrypto
|
|
|
|
endif
|
|
|
|
endif
|
|
|
|
|
|
|
|
CFLAGS += '-DSHA1_HEADER=$(SHA1_HEADER)'
|
|
|
|
|
|
|
|
$(LIB_FILE): $(LIB_OBJS)
|
|
|
|
$(AR) rcs $@ $(LIB_OBJS)
|
|
|
|
|
|
|
|
check:
|
|
|
|
for i in *.c; do sparse $(CFLAGS) $(SPARSE_FLAGS) $$i; done
|
|
|
|
|
|
|
|
test-date: test-date.c date.o
|
|
|
|
$(CC) $(CFLAGS) -o $@ test-date.c date.o
|
|
|
|
|
|
|
|
test-delta: test-delta.c diff-delta.o patch-delta.o
|
|
|
|
$(CC) $(CFLAGS) -o $@ $^
|
|
|
|
|
|
|
|
git-%: %.c $(LIB_FILE)
|
|
|
|
$(CC) $(CFLAGS) -o $@ $(filter %.c,$^) $(LIBS)
|
|
|
|
|
|
|
|
git-update-cache: update-cache.c
|
|
|
|
git-diff-files: diff-files.c
|
|
|
|
git-init-db: init-db.c
|
|
|
|
git-write-tree: write-tree.c
|
|
|
|
git-read-tree: read-tree.c
|
|
|
|
git-commit-tree: commit-tree.c
|
|
|
|
git-cat-file: cat-file.c
|
|
|
|
git-fsck-cache: fsck-cache.c
|
|
|
|
git-checkout-cache: checkout-cache.c
|
|
|
|
git-diff-tree: diff-tree.c
|
|
|
|
git-rev-tree: rev-tree.c
|
|
|
|
git-ls-files: ls-files.c
|
|
|
|
git-check-files: check-files.c
|
|
|
|
git-ls-tree: ls-tree.c
|
|
|
|
git-merge-base: merge-base.c
|
|
|
|
git-merge-cache: merge-cache.c
|
|
|
|
git-unpack-file: unpack-file.c
|
|
|
|
git-export: export.c
|
|
|
|
git-diff-cache: diff-cache.c
|
|
|
|
git-convert-cache: convert-cache.c
|
|
|
|
git-http-pull: http-pull.c pull.c
|
|
|
|
git-local-pull: local-pull.c pull.c
|
|
|
|
git-ssh-push: rsh.c
|
|
|
|
git-ssh-pull: rsh.c pull.c
|
|
|
|
git-rev-list: rev-list.c
|
|
|
|
git-mktag: mktag.c
|
|
|
|
git-diff-helper: diff-helper.c
|
|
|
|
git-tar-tree: tar-tree.c
|
|
|
|
git-hash-object: hash-object.c
|
|
|
|
git-stripspace: stripspace.c
|
|
|
|
git-diff-stages: diff-stages.c
|
|
|
|
git-rev-parse: rev-parse.c
|
|
|
|
git-patch-id: patch-id.c
|
|
|
|
git-pack-objects: pack-objects.c
|
|
|
|
git-unpack-objects: unpack-objects.c
|
|
|
|
git-verify-pack: verify-pack.c
|
|
|
|
git-receive-pack: receive-pack.c
|
|
|
|
git-send-pack: send-pack.c
|
|
|
|
git-prune-packed: prune-packed.c
|
|
|
|
git-fetch-pack: fetch-pack.c
|
|
|
|
git-var: var.c
|
|
|
|
git-peek-remote: peek-remote.c
|
[PATCH] Add update-server-info.
The git-update-server-info command prepares informational files
to help clients discover the contents of a repository, and pull
from it via a dumb transport protocols. Currently, the
following files are produced.
- The $repo/info/refs file lists the name of heads and tags
available in the $repo/refs/ directory, along with their
SHA1. This can be used by git-ls-remote command running on
the client side.
- The $repo/info/rev-cache file describes the commit ancestry
reachable from references in the $repo/refs/ directory. This
file is in an append-only binary format to make the server
side friendly to rsync mirroring scheme, and can be read by
git-show-rev-cache command.
- The $repo/objects/info/pack file lists the name of the packs
available, the interdependencies among them, and the head
commits and tags contained in them. Along with the other two
files, this is designed to help clients to make smart pull
decisions.
The git-receive-pack command is changed to invoke it at the end,
so just after a push to a public repository finishes via "git
push", the server info is automatically updated.
In addition, building of the rev-cache file can be done by a
standalone git-build-rev-cache command separately.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
20 years ago
|
|
|
git-update-server-info: update-server-info.c
|
|
|
|
git-build-rev-cache: build-rev-cache.c
|
|
|
|
git-show-rev-cache: show-rev-cache.c
|
|
|
|
|
|
|
|
git-http-pull: LIBS += -lcurl
|
|
|
|
git-rev-list: LIBS += -lssl
|
|
|
|
|
|
|
|
# Library objects..
|
|
|
|
blob.o: $(LIB_H)
|
|
|
|
tree.o: $(LIB_H)
|
|
|
|
commit.o: $(LIB_H)
|
|
|
|
tag.o: $(LIB_H)
|
|
|
|
object.o: $(LIB_H)
|
|
|
|
read-cache.o: $(LIB_H)
|
|
|
|
sha1_file.o: $(LIB_H)
|
|
|
|
usage.o: $(LIB_H)
|
[PATCH] Add update-server-info.
The git-update-server-info command prepares informational files
to help clients discover the contents of a repository, and pull
from it via a dumb transport protocols. Currently, the
following files are produced.
- The $repo/info/refs file lists the name of heads and tags
available in the $repo/refs/ directory, along with their
SHA1. This can be used by git-ls-remote command running on
the client side.
- The $repo/info/rev-cache file describes the commit ancestry
reachable from references in the $repo/refs/ directory. This
file is in an append-only binary format to make the server
side friendly to rsync mirroring scheme, and can be read by
git-show-rev-cache command.
- The $repo/objects/info/pack file lists the name of the packs
available, the interdependencies among them, and the head
commits and tags contained in them. Along with the other two
files, this is designed to help clients to make smart pull
decisions.
The git-receive-pack command is changed to invoke it at the end,
so just after a push to a public repository finishes via "git
push", the server info is automatically updated.
In addition, building of the rev-cache file can be done by a
standalone git-build-rev-cache command separately.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
20 years ago
|
|
|
rev-cache.o: $(LIB_H)
|
|
|
|
strbuf.o: $(LIB_H)
|
|
|
|
gitenv.o: $(LIB_H)
|
|
|
|
entry.o: $(LIB_H)
|
|
|
|
diff.o: $(LIB_H) diffcore.h
|
|
|
|
diffcore-rename.o : $(LIB_H) diffcore.h
|
|
|
|
diffcore-pathspec.o : $(LIB_H) diffcore.h
|
|
|
|
diffcore-pickaxe.o : $(LIB_H) diffcore.h
|
[PATCH] Add -B flag to diff-* brothers.
A new diffcore transformation, diffcore-break.c, is introduced.
When the -B flag is given, a patch that represents a complete
rewrite is broken into a deletion followed by a creation. This
makes it easier to review such a complete rewrite patch.
The -B flag takes the same syntax as the -M and -C flags to
specify the minimum amount of non-source material the resulting
file needs to have to be considered a complete rewrite, and
defaults to 99% if not specified.
As the new test t4008-diff-break-rewrite.sh demonstrates, if a
file is a complete rewrite, it is broken into a delete/create
pair, which can further be subjected to the usual rename
detection if -M or -C is used. For example, if file0 gets
completely rewritten to make it as if it were rather based on
file1 which itself disappeared, the following happens:
The original change looks like this:
file0 --> file0' (quite different from file0)
file1 --> /dev/null
After diffcore-break runs, it would become this:
file0 --> /dev/null
/dev/null --> file0'
file1 --> /dev/null
Then diffcore-rename matches them up:
file1 --> file0'
The internal score values are finer grained now. Earlier
maximum of 10000 has been raised to 60000; there is no user
visible changes but there is no reason to waste available bits.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
20 years ago
|
|
|
diffcore-break.o : $(LIB_H) diffcore.h
|
|
|
|
diffcore-order.o : $(LIB_H) diffcore.h
|
|
|
|
epoch.o: $(LIB_H)
|
|
|
|
|
|
|
|
git-core.spec: git-core.spec.in Makefile
|
|
|
|
sed -e 's/@@VERSION@@/$(GIT_VERSION)/g' < $< > $@
|
|
|
|
|
|
|
|
GIT_TARNAME=git-core-$(GIT_VERSION)
|
|
|
|
dist: git-core.spec git-tar-tree
|
|
|
|
./git-tar-tree HEAD $(GIT_TARNAME) > $(GIT_TARNAME).tar
|
|
|
|
@mkdir -p $(GIT_TARNAME)
|
|
|
|
@cp git-core.spec $(GIT_TARNAME)
|
|
|
|
tar rf $(GIT_TARNAME).tar $(GIT_TARNAME)/git-core.spec
|
|
|
|
@rm -rf $(GIT_TARNAME)
|
|
|
|
gzip -f -9 $(GIT_TARNAME).tar
|
|
|
|
|
|
|
|
rpm: dist
|
|
|
|
$(RPMBUILD) -ta git-core-$(GIT_VERSION).tar.gz
|
|
|
|
|
|
|
|
test: all
|
|
|
|
$(MAKE) -C t/ all
|
|
|
|
|
|
|
|
doc:
|
|
|
|
$(MAKE) -C Documentation all
|
|
|
|
|
|
|
|
install-tools:
|
|
|
|
$(MAKE) -C tools install
|
|
|
|
|
|
|
|
install-doc:
|
|
|
|
$(MAKE) -C Documentation install
|
|
|
|
|
|
|
|
clean:
|
|
|
|
rm -f *.o mozilla-sha1/*.o ppc/*.o $(PROG) $(LIB_FILE)
|
|
|
|
rm -f git-core-*.tar.gz git-core.spec
|
|
|
|
$(MAKE) -C tools/ clean
|
|
|
|
$(MAKE) -C Documentation/ clean
|
|
|
|
|
|
|
|
backup: clean
|
|
|
|
cd .. ; tar czvf dircache.tar.gz dir-cache
|