summaryrefslogtreecommitdiff
path: root/git-resolve-script
AgeCommit message (Collapse)AuthorFilesLines
2005-06-14Trivial git script fixupsLibravatar Linus Torvalds1-0/+0
Fix permissions, and add trivial "reset" and "add" scripts. The "reset" script just resets the index back to head, while the "add" script is just a crutch for people used to do "cvs add".
2005-06-08Make "git commit" work correctly in the presense of a manual mergeLibravatar Linus Torvalds1-1/+2
This has gotten only very light testing, but something like this is clearly necessary and did the right thing for the one case I threw at it.
2005-06-08Make default merge messages denser.Libravatar Linus Torvalds1-2/+1
In particular, make them readable on one line since that's what all the tools like git-shortlog and gitk end up showing.
2005-06-06git-resolve-script: stop when the automated merge failsLibravatar Linus Torvalds1-1/+5
No point in doing a tree write that will just throw confusing messages on the screen.
2005-06-06git-resolve-script: don't wait for three seconds any moreLibravatar Linus Torvalds1-3/+0
We used to overwrite peoples dirty state. We don't any more. So don't print the scary message and don't delay, just do the update already.
2005-06-05More work on merging with git-read-tree..Libravatar Linus Torvalds1-4/+2
Add a "-u" flag to update the tree as a result of a merge. Right now this code is way too anal about things, and fails merges it shouldn't, but let me fix up the different cases and this will allow for much smoother merging even in the presense of dirty data in the working tree.
2005-06-05git-read-tree: be a lot more careful about merging dirty treesLibravatar Linus Torvalds1-2/+3
We don't want to overwrite state that we haven't committed yet when merging, so it's better to make git-read-tree fail than end up with a merge tree that ends up not having the dirty changes. Update git-resolve-script to fail cleanly when git-read-tree fails.
2005-05-30git-resolve-script: use "git-apply --stat" instead of diffstatLibravatar Linus Torvalds1-2/+2
Not everybody necessarily even has diffstat installed.
2005-05-25[PATCH] optimize git-resolve-scriptLibravatar Jeff Garzik1-2/+2
This change was suggested for my git-switch-tree script, and the same issues apply to core git's git-resolve-script as well.
2005-05-09Introduce GIT_DIR environment variable.Libravatar Junio C Hamano1-5/+10
During the mailing list discussion on renaming GIT_ environment variables, people felt that having one environment that lets the user (or Porcelain) specify both SHA1_FILE_DIRECTORY (now GIT_OBJECT_DIRECTORY) and GIT_INDEX_FILE for the default layout would be handy. This change introduces GIT_DIR environment variable, from which the defaults for GIT_INDEX_FILE and GIT_OBJECT_DIRECTORY are derived. When GIT_DIR is not defined, it defaults to ".git". GIT_INDEX_FILE defaults to "$GIT_DIR/index" and GIT_OBJECT_DIRECTORY defaults to "$GIT_DIR/objects". Special thanks for ideas and discussions go to Petr Baudis and Daniel Barkalow. Bugs are mine ;-) Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-05-05Fix git-resolve-script.Libravatar Linus Torvalds1-1/+1
I'd stupidly forgotten one merge_head -> merge conversion, and all my tests were for the fast-forward case that never triggered the bug.
2005-05-05Split "git-pull-script" into two partsLibravatar Linus Torvalds1-0/+56
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.