Eric Blake wrote:
> On 10/25/2012 05:12 PM, Laine Stump wrote:
>>
>> What would be *really* nice is if git could give a *warning* if you
>> tried to do git add . and it found any of those files - it would prevent
>> the cases where you forget to save a file that you've modified.
If you write Chang
On 10/25/2012 05:12 PM, Laine Stump wrote:
>
> What would be *really* nice is if git could give a *warning* if you
> tried to do git add . and it found any of those files - it would prevent
> the cases where you forget to save a file that you've modified.
I suppose it IS possible to make 'git com
On 10/25/2012 06:44 PM, Eric Blake wrote:
> On 10/25/2012 04:38 PM, Laine Stump wrote:
>> On 10/25/2012 06:15 PM, Eric Blake wrote:
>>> I did a 'git add .', then realized that it ended up trying to
>>> add the emacs lock file for a corresponding file that I had not
>>> yet saved all my edits; thank
On 10/25/2012 04:38 PM, Laine Stump wrote:
> On 10/25/2012 06:15 PM, Eric Blake wrote:
>> I did a 'git add .', then realized that it ended up trying to
>> add the emacs lock file for a corresponding file that I had not
>> yet saved all my edits; thankfully I noticed it in time. Since
>> we already
On 10/25/2012 06:15 PM, Eric Blake wrote:
> I did a 'git add .', then realized that it ended up trying to
> add the emacs lock file for a corresponding file that I had not
> yet saved all my edits; thankfully I noticed it in time. Since
> we already exclude other temporary files, this makes the mo
I did a 'git add .', then realized that it ended up trying to
add the emacs lock file for a corresponding file that I had not
yet saved all my edits; thankfully I noticed it in time. Since
we already exclude other temporary files, this makes the most
sense for preventing such a mistake from actual
