Re: What's the use case for committing both the freshly created file and it's exclusion in .gitignore?

On 9 August 2018 at 21:58, Jeff King wrote: > If you are asking as a more general case: why do we not complain about > .gitignore for files the index already knows about, then I think that is > useful. It lets you override the .gitignore _once_ when adding the file > initially, and then you don't

What's the use case for committing both the freshly created file and it's exclusion in .gitignore?

Hi there! I hope that the subject of my message (i.e. the question) is exhaustive enough, so I'll just stick to reproducing my issue. Steps to reproduce: 1. Create a new file. 2. Stage the file. 3. Add the file to .gitignore. 4. Stage the .gitignore. 5. Commit changes. I imagined that the file

Re: Troubles with picking an editor during Git update

Git guidelines states that I should leave cc intact. I have altered it, as I wanted to reply to both of you. I hope that my approach can be considered acceptable. Johannes, I see the following line in the piece of code you quoted:

Troubles with picking an editor during Git update

Hi there! I had an issue with Git installer for Windows while trying to update my instance of the software. My previous version was "git version 2.15.1.windows.2", while my operating system prompted me to upgrade to "2.17.0". The installer asked me to "choose the default editor for Git". One of