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

Teach git-gui about merging around modified files?

From
Brian Downing <bdowning@lavos.net>
Date
Jul 27, 2007, 17:03 UTC
Message-ID
<20070727170347.GX21692@lavos.net>

"git merge" will happily merge a change with modified files in the tree as long as the merge doesn't touch any of them. However, it appears "git gui" won't even try if there are modified files at all.

How hard would it be to fix this, or is this an intentional choice? I realize that commiting even untouched files before a merge is safer, but I'm tasked with migrating some CVS users to Git, and I'd prefer to be able to introduce the new Git workflow slowly.

(I'm happy enough with disallowing merges that actually touch modified files, so I'm not looking for any kind of in-working-directory merge like some others were. I'd just like the "git merge" behavior to work in git-gui.)

-bcd
Next: Shawn O. Pearce
Message 1 of 3 in “Teach git-gui about merging around modified files?”
  1. Brian DowningJul 27, 2007
  2. Shawn O. PearceJul 29, 2007
  3. Shawn O. PearceJul 29, 2007

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.