On Fri, Mar 17, 2017 at 5:23 PM, Junio C Hamano wrote:
> Nevada Sanchez writes:
>
>> Here's an easy to reproduce bug. It's the only example I know of where
>> git legitimately loses data in a way that is unrecoverable,
>> unexpected, and without warning.
>
> This is an example of a user explicitl
On Sat, Mar 18, 2017 at 5:02 AM, Jonathan Nieder wrote:
> Junio C Hamano wrote:
>
>> There is no "untracked but precious" vs "untracked and expendable"
>> difference in the current system. An untracked file that matches
>> patterns listed in .gitignore is treated as the latter.
> [...]
>> We've d
Jonathan Nieder writes:
> The most recent example I can find is 2010:
> http://public-inbox.org/git/4c6a1c5b.4030...@workspacewhiz.com/.
>
> It also came up in 2007:
> http://public-inbox.org/git/c0e9f681e68d48eb8989022d11fee...@ntdev.corp.microsoft.com/
> Earlier in that year it even made the "W
On Fri, Mar 17, 2017 at 2:23 PM, Junio C Hamano wrote:
> We've discussed the lack of "untracked but precious" class a few
> times on the list in the past, but I do not recall the topic came up
> in the recent past. It perhaps is because nobody found that class
> useful enough so far.
My gut reac
Junio C Hamano wrote:
> There is no "untracked but precious" vs "untracked and expendable"
> difference in the current system. An untracked file that matches
> patterns listed in .gitignore is treated as the latter.
[...]
> We've discussed the lack of "untracked but precious" class a few
> times
Hi Nevada,
Nevada Sanchez wrote:
> # Commit a file that will end up in .gitignore
> echo 'original settings' > mine.conf
> git add mine.conf
> git commit -m "Unknowingly committed my settings."
>
> echo '*.conf' > .gitignore
> git add .gitignore
> git commit -m "Users shouldn't commit their setti
Nevada Sanchez writes:
> Here's an easy to reproduce bug. It's the only example I know of where
> git legitimately loses data in a way that is unrecoverable,
> unexpected, and without warning.
This is an example of a user explicitly telling git to discard data
and git performing as it is told.
Here's an easy to reproduce bug. It's the only example I know of where
git legitimately loses data in a way that is unrecoverable,
unexpected, and without warning.
```
git --version
# git version 2.12.0
mkdir git-demo
cd git-demo
git init
# Commit a file that will end up in .gitignore
echo 'ori
8 matches
Mail list logo
