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

Re: Stashing individual files

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 3, 2012, 20:08 UTC
Message-ID
<7vfwfwtup7.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20120103190612.GC20926@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> I think that would be OK compromise, though. I'd rather not introduce a
> whole new "stashfiles" command (or even a new subcommand of stash) if we
> can avoid it.
Why wouldn't a simple "git diff -- paths >P.diff" work?

What does such a partial stash leave in the working tree, how does the user deal with the remaining local changes, what happens after such a partial stash is applied/popped?

I wouldn't have worried about such a change before e0e2a9c (stash: drop dirty worktree check on apply, 2011-04-05) but now we allow application of stashed changes to the dirty working tree (which is a very good thing), I am not sure how sensibly these changes in different places would interact if we start supporting partial stashing.

Previous: Jeff KingNext: Jeff King
Message 3 of 6 in “Stashing individual files”
  1. Chris LeongJan 2, 2012
  2. Jeff KingJan 3, 2012
  3. Junio C HamanoJan 3, 2012
  4. Jeff KingJan 3, 2012
  5. Junio C HamanoJan 3, 2012
  6. Tor ArntsenJan 4, 2012

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.