11 USAGE="usage: zit COMMAND FILE [ARGS...]"
23 echo "Set up a git repository under .zit.FILE to track changes for FILE."
24 echo "File must be a regular file and in the current directory."
27 echo " init Synonym for track"
28 echo " list Synonym for tracked"
29 echo " track Start tracking changes to FILE"
30 echo " tracked List tracked files in current directory"
32 echo "See 'zit help git' or 'git help' for git commands."
39 test $ZIT_FILE || abort "Please specify a file"
40 test -f $ZIT_FILE || abort "No such file $ZIT_FILE"
41 test $ZIT_FILE = "`basename $ZIT_FILE`" || abort "Sorry, Zit only works on files in the current directory"
42 export GIT_DIR=".$ZIT_FILE.git"
43 export GIT_WORK_TREE="`pwd`"
48 test -e $GIT_DIR && abort "$GIT_DIR exists, is $ZIT_FILE tracked already?"
49 mkdir $GIT_DIR && echo "Initializing Zit repository in $GIT_DIR"
50 test -d $GIT_DIR || abort "Failed to create $GIT_DIR"
51 git init || abort "Failed to initialize Git repository in $GIT_DIR"
52 echo "*" > $GIT_DIR/info/exclude
53 git add -f $ZIT_FILE || abort "Failed to add $ZIT_FILE"
54 git commit "$@" || abort "Failed to make first commit for $ZIT_FILE"
58 export GIT_WORK_TREE="`pwd`"
59 for file in .*.git; do
60 if ! test -e $file; then
61 echo "(no files tracked by zit)"
64 export GIT_DIR="$file"
67 # TODO show actual file status
85 # Most commands will work with the generic catch-all mechanism used
86 # below, but some of them require a more thorough analysis of the
87 # parameters to decide whether $ZIT_FILE should be put back into the
88 # parameter list or not. For example,
89 # $ zit commit somefile
90 # wouldn't do what one expects it to do, unless 'add' is run first,
93 # wouldn't work either), however
94 # $ zit commit somefile -a
95 # would work correctly. So we handle some commands separately (for the
96 # moment just add and commit)
100 git $cmd "$@" "$ZIT_FILE"
102 # the raw<command> method can be used to not replicate $ZIT_FILE in the