From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ed Avis Subject: Re: Feature: git stash pop --always-drop Date: Mon, 10 Aug 2015 13:43:07 +0000 (UTC) Message-ID: References: <20150810124125.GC32371@sigill.intra.peff.net> <20150810133220.GA3559@sigill.intra.peff.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: git@vger.kernel.org X-From: git-owner@vger.kernel.org Mon Aug 10 15:43:37 2015 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZOnMR-000612-Qf for gcvg-git-2@plane.gmane.org; Mon, 10 Aug 2015 15:43:32 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753993AbbHJNnX (ORCPT ); Mon, 10 Aug 2015 09:43:23 -0400 Received: from plane.gmane.org ([80.91.229.3]:35595 "EHLO plane.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753799AbbHJNnT (ORCPT ); Mon, 10 Aug 2015 09:43:19 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZOnMD-0005vc-Ev for git@vger.kernel.org; Mon, 10 Aug 2015 15:43:17 +0200 Received: from 80.169.169.174 ([80.169.169.174]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 10 Aug 2015 15:43:17 +0200 Received: from eda by 80.169.169.174 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 10 Aug 2015 15:43:17 +0200 X-Injected-Via-Gmane: http://gmane.org/ X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 80.169.169.174 (Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:39.0) Gecko/20100101 Firefox/39.0 Cyberfox/39.0) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Jeff King peff.net> writes: >>An alternative would be for git stash to always print the name of the stash >>it is applying. > Applying refs/stash@{0} (31cb86c3d700d241e315d989f460e3e83f84fa19) Yes, that's the one. >Or maybe it would be useful to actually show the stash subject, That could be nice to see, but is not a substitute for the SHA. If the stash pop failed because of conflicts then it could even print To drop this stash manually, run 'git stash drop abcde...' Another feature I would like to see is a kind of atomic stash apply, where either the whole change can be applied to the working tree without conflicts, or nothing happens. -- Ed Avis