# feature suggestion: git commit -a -o ... 2 messages from 2009-06-25 to 2009-06-26. Participants: David Reitter, Jeff King. Thread: https://gitlist.dev/t/19936 ## David Reitter, 2009-06-25 20:39 Subject: feature suggestion: git commit -a -o ... Message-ID: URL: https://gitlist.dev/e/F9B3FF44-FC23-4ADA-A933-9BED857AB469%40gmail.com ``` I'm wondering why "git commit -a -o *" is not supported. With this command I'd like to commit the intersection of all changed, tracked files and those in the current directory. I found that "git commit ." does what I want and it even detects deleted files (excellent, thank you). ``` ## Jeff King, 2009-06-26 06:34 Subject: Re: feature suggestion: git commit -a -o ... Message-ID: <20090626063435.GA12283@coredump.intra.peff.net> URL: https://gitlist.dev/e/20090626063435.GA12283%40coredump.intra.peff.net In-Reply-To: ``` On Thu, Jun 25, 2009 at 04:39:32PM -0400, David Reitter wrote: > I'm wondering why "git commit -a -o *" is not supported. > With this command I'd like to commit the intersection of all changed, > tracked files and those in the current directory. > > I found that "git commit ." does what I want and it even detects > deleted files (excellent, thank you). I don't understand what "-a" is supposed to be doing there. It means "all tracked files in the whole repo". But from your "git commit ." example, it sounds like you just want "git commit -o *" (in fact, "git commit ." is more or less equivalent (with the except of dot-files) to "git commit *", which is in turn the same as "git commit -o *"). Can you be more clear about the set of files you have, the set you want to commit, and how "git commit" differs from your expectations? -Peff ```