Jonathan Nieder <jrnieder <at> gmail.com> writes: > Hmm, the "git add" manual suggests it is the other way around: > > -A, --all > Like -u, but match <filepattern> against files in the working > tree in addition to the index. That means that it will find new > files as well as staging modified content and removing files > that are no longer in the working tree. > > So I would expect "git add -A" to do the same thing as "git add -u", > plus handling added files. > > Maaartin, could you give an example showing where add -A goes wrong? I can't, since I was wrong. These commits have two parents (I'm not sure if this is a good idea), and that's why I saw no changes in the log. Actually, "git add - A" does everything I need, and with "/bin/cp .git/index $GIT_INDEX_FILE" everything seems to work. Sorry for the noise. -- 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