On Tue, May 12, 2009 at 11:18:25AM -0400, Andrew Schein wrote: > The [1] in my prompt indicates the exit code of the git commands. What > I find odd is that even with the -q option, you get this verbose > output. Also, you get a non-zero exit status (which I would expect > only on a failure such as presence of an unresolved conflict). My git > usage is to have a number of small repositories and use a shell script > to loop over them and perform a sync with a centralized server. > Having all this wordy output on a "no sync necessary" scenario seems > counter the desired properties of output only when work is taking > place or when an error occurs. > > Have others developed git practices to sync a bunch or repositories > without all this verbose output on a "no change" scenario? Yes, I have such a script. I check: git ls-files -m -o -d --exclude-standard --directory --no-empty-directory If it produces any output, then there is something to commit (either a change in a tracked file, or an untracked file that might need to be added). I also do a fetch and check to see if we have any commits that need to be merged: git rev-list master..origin or any commits that we need to push: git rev-list origin..master (actually, it is a bit more complicated, since "master" and "origin" are just convention; I actually parse the config to find the branch pairs). -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html