Re: Removing an individual stashed state

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Martin Langhoff wrote:
That's not so bad -- I didn't expect it to be gone.

Once you've applied a stash, is it still useful? I don't see any point keeping it around, given that a stash is supposed to be a temporary holding area for dirty working trees.

If people are keeping stashes around to apply them in multiple places, it seems like that'd be better handled by an actual branch and/or "git cherry-pick". Git already has the "persistent edits that can be reapplied to different commits" thing well-covered; I don't see any point in supporting that use case in the stash command as well.

Well, I guess I should make that less of a statement than a question for people who think it's expected behavior for a stash to stick around after it's applied: Why do you think that's good behavior? What useful things does it let you do?

-Steve (who thinks someday stash, rebase -i, and StGIT/guilt will converge as part of core git)
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux