git-ls-files --unmerged implies --stages: ?
- From
Matthias Urlichs <smurf@smurf.noris.de>
- Date
- Mar 9, 2006, 15:19 UTC
- Message-ID
- <pan.2006.03.09.15.19.03.286472@smurf.noris.de>
Hi,
I wonder why git-ls-files --unmerged implies --stages. One nice use case for this command is to edit all the conflicting files after a failed merge, i.e.
$ vi $(git-ls-files --unmerged)
except I need a pipe to throw out all the cruft in there.
Does anybody depend on that implication, or do I need to add a "no-stages" option, or am I blind and there's a better way to do this?
-- Matthias Urlichs