Re: git stash --include-untracked possible destructive behavior

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

Subject: Re: git stash --include-untracked possible destructive behavior
From: Marc Strapetz <marc.strapetz@xxxxxxxxxxx>
Date: Fri, 9 Jun 2017 10:28:21 +0200
Cc: git@xxxxxxxxxxxxxxx
In-reply-to: <e45eed21-f808-b2a8-a01b-78c18a9c343a@teichroeb.net>
References: <2b695c73-9de2-5502-6d19-ba4ad0114978@syntevo.com> <197975d0-7ec3-0ff4-9201-48226fd3b60c@teichroeb.net> <20170608222949.GA121539@google.com> <e45eed21-f808-b2a8-a01b-78c18a9c343a@teichroeb.net>
User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1

On 09.06.2017 00:39, Joel Teichroeb wrote:

Looks like that series was merged last week, fixing this issue.

Marc, the fix will probably be in git 2.14.

Thanks, I can confirm that with current master "git clean" as well as"git stash" are working properly now (tested on Linux). I'm lookingforward to version 2.14.


-Marc

References:
- git stash --include-untracked possible destructive behavior
  - From: Marc Strapetz
- Re: git stash --include-untracked possible destructive behavior
  - From: Joel Teichroeb
- Re: git stash --include-untracked possible destructive behavior
  - From: Brandon Williams
- Re: Re: git stash --include-untracked possible destructive behavior
  - From: Joel Teichroeb

Prev by Date: Re: [PATCH 1/2] add setup step to filter-branch
Next by Date: [PATCH 0/2] Add a freez() wrapper
Previous by thread: Re: Re: git stash --include-untracked possible destructive behavior
Next by thread: "There are too many unreachable loose objects" - why don't we run 'git prune' automatically?
Index(es):
- Date
- Thread

[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]