From: Brandon Williams <bmwill@google.com>
To: Joel Teichroeb <joel@teichroeb.net>
Cc: Marc Strapetz <marc.strapetz@syntevo.com>, git@vger.kernel.org
Subject: Re: git stash --include-untracked possible destructive behavior
Date: Thu, 8 Jun 2017 15:29:49 -0700 [thread overview]
Message-ID: <20170608222949.GA121539@google.com> (raw)
In-Reply-To: <197975d0-7ec3-0ff4-9201-48226fd3b60c@teichroeb.net>
On 06/08, Joel Teichroeb wrote:
> It looks like it's an issue with git clean, as that's what stash
> uses internally. You can try your same test, but replace git stash
> with "git clean -df" and it will delete Data. Maybe clean should
> check if there are any ignored files in an untracked directory and
> only remove it if -x is specified?
>
> Joel
There was someone working on fixing clean, you can look at the patch
series at
https://public-inbox.org/git/20170523100937.8752-1-sxlijin@gmail.com/
though I'm unsure of the series' status.
--
Brandon Williams
next prev parent reply other threads:[~2017-06-08 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 11:52 git stash --include-untracked possible destructive behavior Marc Strapetz
2017-06-08 22:13 ` Joel Teichroeb
2017-06-08 22:29 ` Brandon Williams [this message]
2017-06-08 22:39 ` Joel Teichroeb
2017-06-09 8:28 ` Marc Strapetz
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=20170608222949.GA121539@google.com \
--to=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=joel@teichroeb.net \
--cc=marc.strapetz@syntevo.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).