git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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
Next: Junio C Hamano
Message 1 of 2 in “git-ls-files --unmerged implies --stages: ?”
  1. Matthias UrlichsMar 9, 2006
  2. Junio C HamanoMar 9, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.