summaryrefslogtreecommitdiff
path: root/git-pull-script
AgeCommit message (Collapse)AuthorFilesLines
2005-05-06Add http and local transport support for git-pull-script.Libravatar Junio C Hamano1-6/+31
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-05-05Split "git-pull-script" into two partsLibravatar Linus Torvalds1-45/+1
Separate out the merge resolve from the actual getting of the data. Also, update the resolve phase to take advantage of the fact that we don't need to do the commit->tree object lookup by hand, since all the actors involved happily just act on a commit object these days.
2005-05-05git-pull-script: do the diffstat also for the fast-forward caseLibravatar Linus Torvalds1-0/+1
This way you always see what the state change was.
2005-05-04Teach "git-pull-script" about alternate HEAD's to pull..Libravatar Linus Torvalds1-2/+3
People are already starting to use a multi-head model.
2005-05-04git-pull-script: add a final "diffstat" to show the result of the merge.Libravatar Linus Torvalds1-0/+1
This is useful to verify that you got the right thing.
2005-04-29Update the merge scripts for the big git rename.Libravatar Linus Torvalds1-11/+11
Let's see what else I forgot..
2005-04-29[PATCH] GIT: Honour SHA1_FILE_DIRECTORY env var in git-pull-scriptLibravatar Rene Scharfe1-1/+1
If you set SHA1_FILE_DIRECTORY to something else than .git/objects git-pull-script will store the fetched files in a location the rest of the tools does not expect. git-prune-script also ignores this setting, but I think this is good, because pruning a shared tree to fit a single project means throwing away a lot of useful data. :-) Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-04-26git-pull-script: do automatic mergesLibravatar Linus Torvalds1-3/+11
When the trivial "read-tree" merge fails, fall back on the (equally trivial) automatic merge script instead of forcing the user to do it by hand. When _that_ fails, you get to do a manual merge.
2005-04-19Update "git-pull-script" to use "read-tree -m" forLibravatar Linus Torvalds1-2/+2
reading a single tree too. That should speed up a trivial merge noticeably. Also, don't bother reading back the tree we just wrote when we committed a real merge. It had better be the same one we still have..
2005-04-19Make git-pull-script do the right thing for symlinked HEAD's.Libravatar Linus Torvalds1-1/+3
Also exit gracefully if the HEAD pull failed, rather than use a possibly stale MERGE_HEAD.
2005-04-18[PATCH] Do not let rsync obliterate .git/object symbolic link.Libravatar Junio C Hamano1-1/+1
Signed-off-by: Junio C Hamano <junkio@cox.net> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-04-18Add "update-cache --refresh" to git-pull-script to make sureLibravatar Linus Torvalds1-2/+2
out index is all ready to go after a pull. Noted by Russell King
2005-04-18Add the simple scripts I used to do a merge with content conflicts.Libravatar Linus Torvalds1-0/+46
They sure as hell aren't perfect, but they allow you to do: ./git-pull-script {other-git-directory} to do the initial merge, and if that had content clashes, you do merge-cache ./git-merge-one-file-script -a which tries to auto-merge. When/if the auto-merge fails, it will leave the last file in your working directory, and you can edit it and then when you're happy you can do "update-cache filename" on it. Re-do the merge-cache thing until there are no files left to be merged, and now you can write the tree and commit: write-tree commit-tree .... -p $(cat .git/HEAD) -p $(cat .git/MERGE_HEAD) and you're done.