From: David Caldwell <david@porkrind.org>
To: Marc Branchaud <marcnarc@xiplink.com>,
Paul Ebermann <Paul.Ebermann@esperanto.de>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Johannes Sixt <j.sixt@viscovery.net>,
Andrew Wong <andrew.w@sohovfx.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] stash: Add --clean option to stash and remove all untracked files
Date: Tue, 21 Jun 2011 22:49:22 -0700 [thread overview]
Message-ID: <FD779A88A6134648D999E7C7@black.porkrind.org> (raw)
On 6/21/11 5:23 PM -0400 Marc Branchaud wrote:
> On 11-06-21 12:11 PM, Paul Ebermann wrote:
>>
>> I think `--also-untracked` sounds better. It is even longer, though.
>>
>> There could also be `--only-untracked`, which would stack only the
>> untracked files (and let changes of tracked files there).
>
> Perhaps -uall to match git-status's -u[<mode>] option (and also the long
> version thereof)?
Currently I'm playing with --include-untracked (-u) and --all (-a) while I
fix a bug I found in the patch. I agree that --untracked sounds like it's
only stashing the untracked files which isn't the case. I wasn't going to
have an option to stash *just* the untracked files because I can't come up
with a use case that makes sense. I still like "--clean", too.
-uall (like git status) isn't really the same thing which I think is
confusing since it has the same name.
-David
next reply other threads:[~2011-06-22 5:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 5:49 David Caldwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-20 23:36 [PATCH] stash: Add --clean option to stash and remove all untracked files David Caldwell
2011-06-21 0:38 ` Jeff King
2011-06-21 1:36 ` David Caldwell
2011-06-21 5:08 ` Andrew Wong
2011-06-21 6:28 ` Johannes Sixt
2011-06-21 14:18 ` Jeff King
2011-06-21 16:11 ` Paul Ebermann
2011-06-21 21:23 ` Marc Branchaud
2011-06-22 7:47 ` Miles Bader
2011-06-22 15:00 ` Jeff King
2011-06-21 17:16 ` Junio C Hamano
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=FD779A88A6134648D999E7C7@black.porkrind.org \
--to=david@porkrind.org \
--cc=Paul.Ebermann@esperanto.de \
--cc=andrew.w@sohovfx.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=marcnarc@xiplink.com \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.