Jakub Narebski <jnareb@xxxxxxxxx> writes: > Seth Falcon wrote: >> Spelling out a bunch of files spread around your tree for update-index >> can be annoying. Some way of marking a list seems natural. Maybe >> that is a separate issue. > > Perhaps git-commit should also accept --exclude=<pattern> option? > Would that help? I don't think I understand what an --exclude=<pattern> option would do, but I'm pretty sure it doesn't help the use case I'm thinking of: Editing away, you've made changes in 8 files. Reviewing diff, you want to commit 6 of those and continue working on the other two. It seems that there could be a less manual way than git update-index f1 f2 ... f6 Hmm, maybe I could do: git diff --name-only > changed ## edit changed cat changed|xargs git update-index I suppose this could be wrapped in a simple way to bring up an editor. + seth - 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