git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brandon Casey <casey@nrlssc.navy.mil>
To: Marco Costalba <mcostalba@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git stash: one bug and one feature request
Date: Fri, 4 Jan 2008 10:36:01 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0801041030420.31161@torch.nrlssc.navy.mil> (raw)
In-Reply-To: <e5bfff550801040814n82f34b2g17c485a207093440@mail.gmail.com>

On Fri, 4 Jan 2008, Marco Costalba wrote:

> Currently git-stash writes to stderr also if there is nothing to error
> out, also it would be very nice ;-) if git 'stash clear command' would
> support deleting of only one patch, so as example to write
>
> stg stash clear stash@{0}
>
> To remove only the last added.

Maybe it should be named 'drop'. 'drop' sounds better than
'clear' for this usage.

   git stash drop [<stash>]

Not sure how often such a command would be used though, so
it may not be worth it.

-brandon

  reply	other threads:[~2008-01-04 17:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-04 16:14 [PATCH] git stash: one bug and one feature request Marco Costalba
2008-01-04 16:36 ` Brandon Casey [this message]
2008-01-04 17:30   ` Pascal Obry
2008-01-04 17:51     ` Jakub Narebski
2008-01-04 19:36       ` Brian Swetland
2008-01-04 21:04       ` Jeff King
     [not found]     ` <e5bfff550801040944p7f8e722asfa726b34a4a712fa@mail.gmail.com>
2008-01-04 18:00       ` Brandon Casey
2008-01-04 18:05         ` Marco Costalba
2008-01-04 18:34           ` Brandon Casey
2008-01-04 18:46             ` Marco Costalba
2008-01-05  0:31               ` Junio C Hamano
2008-01-05  0:29 ` Junio C Hamano
2008-01-05  8:25   ` Marco Costalba
2008-01-05  8:36     ` Junio C Hamano
2008-01-05  8:57       ` Marco Costalba
2008-01-05  9:06     ` Junio C Hamano
2008-01-05  6:41 ` Wayne Davison
2008-01-05  6:52   ` Junio C Hamano
2008-01-05  8:31     ` Marco Costalba

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0801041030420.31161@torch.nrlssc.navy.mil \
    --to=casey@nrlssc.navy.mil \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mcostalba@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).