org/kernel/git.git - forked from git/git

	Commit message (Collapse)	Author	Age
*	Refuse to create funny refs in clone-pack, git-fetch and receive-pack.	Junio C Hamano	2005-10-15
\| \| \| \| \| \| \| \|	Using git-check-ref-format, make sure we do not create refs with funny names when cloning from elsewhere (clone-pack), fast forwarding local heads (git-fetch), or somebody pushes into us (receive-pack). Signed-off-by: Junio C Hamano <junkio@cox.net>
*	Revert "Replace zero-length array decls with []."	Junio C Hamano	2005-08-29
\| \| \| \| \| \| \| \| \| \| \| \| \|	This reverts 6c5f9baa3bc0d63e141e0afc23110205379905a4 commit, whose change breaks gcc-2.95. Not that I ignore portability to compilers that are properly C99, but keeping compilation with GCC working is more important, at least for now. We would probably end up declaring with "name[1]" and teach the allocator to subtract one if we really aimed for portability, but that is left for later rounds. Signed-off-by: Junio C Hamano <junkio@cox.net>
*	Replace unsetenv() and setenv() with older putenv().	Jason Riedy	2005-08-23
\| \| \| \| \| \| \| \| \| \| \|	Solaris 8 doesn't have the newer unsetenv() and setenv() functions, so replace them with putenv(). The one use of unsetenv() in fsck-cache.c now sets GIT_ALTERNATE_OBJECT_ DIRECTORIES to the empty string. Every place that var is used, NULLs are also replaced with empty strings, so it's ok. Signed-off-by: Jason Riedy <ejr@cs.berkeley.edu>
*	Replace zero-length array decls with [].	Jason Riedy	2005-08-23
\| \| \| \| \| \|	C99 denotes variable-sized members with [], not [0]. Signed-off-by: Jason Riedy <ejr@cs.berkeley.edu>
*	Make sure leading directories exist when pushing refs.	Junio C Hamano	2005-08-02
\| \| \| \| \| \| \| \| \|	It does not matter if the only refs you push are directly underneath heads and tags, but we forgot to make sure we have leading directories so pushing tags/v0.99/1 would not have worked. Signed-off-by: Junio C Hamano <junkio@cox.net>
*	receive-pack hooks updates.	Junio C Hamano	2005-08-02
\| \| \| \| \| \| \| \|	The earlier one conflated update and post-update hooks for no good reason. Correct that ugly hack. Now post-update hooks will take the list of successfully updated refs. Signed-off-by: Junio C Hamano <junkio@cox.net>
*	[PATCH] Fix warning about non-void return in a void function.	A Large Angry SCM	2005-08-01
\| \| \| \| \|	Signed-off-by: A Large Angry SCM <gitzilla@gmail.com> Signed-off-by: Junio C Hamano <junkio@cox.net>
*	[PATCH] Added hook in git-receive-pack	Josef Weidendorfer	2005-07-31
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Just before updating a ref, $GIT_DIR/hooks/update refname old-sha1 new-sha1 is called if executable. The hook can decline the ref to be updated by exiting with a non-zero status, or allow it to be updated by exiting with a zero status. The mechanism also allows e.g sending of a mail with pushed commits on the remote repository. Documentation update with an example hook is included. jc: The credits of the basic idea and initial implementation go to Josef, but I ended up rewriting major parts of his patch, so bugs are all mine. Also I changed the semantics for the hook from his original version (which were post-update hook) so that the hook can optionally decline to update the ref, and also can be used to implement the overall cleanups. The latter was primarily to implement a suggestion from Linus that calling update-server-info should be made optional. Signed-off-by: Junio C Hamano <junkio@cox.net>
*	[PATCH] Add update-server-info.	Junio C Hamano	2005-07-23
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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>
*	Make "upload-pack" match git-fetch-pack usage	Linus Torvalds	2005-07-08
\| \| \| \| \|	Do the default "try xyz.git xyz fails" thing for the directory we get passed in.
*	[PATCH] Let umask do its work upon filesystem object creation.	Junio C Hamano	2005-07-06
\| \| \| \| \| \| \| \|	IIRC our strategy was to let the users' umask take care of the final mode bits. This patch fixes places that deviate from it. Signed-off-by: Junio C Hamano <junkio@cox.net> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
*	Fix sparse warnings.	Linus Torvalds	2005-07-03
\| \| \| \| \|	Mainly making a lot of local functions and variables be marked "static", but there was a "zero as NULL" warning in there too.
*	Fix up "for_each_ref()" to be more usable, and use it in git-fsck-cache	Linus Torvalds	2005-07-03
\| \| \| \| \|	It needed to take the GIT_DIR information into account, something that the original receive-pack usage just never cared about.
*	Generalize the "show each ref" code in receice-pack	Linus Torvalds	2005-07-02
\| \| \| \|	This turns it into a generic "do xyz for each ref" library function.
*	Do ref matching on the sender side rather than on receiver	Linus Torvalds	2005-06-30
\| \| \| \| \| \| \| \| \| \| \| \|	This makes the receiver always send a full list of valid refs, which will allow us to do better packs, as well as handle creation of new refs. Eventually. Right now we just moved the matching and enabled it. So now you can do git-send-pack host:path branch1 branch2 to only send branches "branch1" and "branch2".
*	Add support for "forcing" a ref on the remote side	Linus Torvalds	2005-06-30
\| \| \| \| \| \| \| \| \|	A "old ref" of all zeroes is considered a "don't care" ref, and allows us to say "write the new ref regardless of what the old ref contained (or even if it existed at all)". This allows (if git-send-pack were to do it) creating new refs, and fixing up old ones.
*	git-receive-pack: implement ref switch command handling	Linus Torvalds	2005-06-30
\| \| \| \| \| \|	After unpacking the object pack successfully, we go through the list of refs, and verify that they still contain their expected values. Then we replace them with the new ones.
*	git-receive-pack: start parsing ref update commands	Linus Torvalds	2005-06-29
\| \| \| \|	We don't act on them yet, but we parse them.
*	Slow but steady progress on git pack receive/send	Linus Torvalds	2005-06-29
\|
*	Make send/receive-pack be closer to doing something interesting	Linus Torvalds	2005-06-29
\|
*	Add first cut at "git-receive-pack"	Linus Torvalds	2005-06-29
	It's not working yet, but it's at the point where I want to be able to track my changes. The theory of operation is that this is the "remote" side of a "git push". It can tell us what references the remote side has, receives out reference update commands and a pack-file, and can execute the unpacking command.