Re: [PATCH] unpack-trees: do not delete i-t-a entries in worktree even when forced

2016-02-25 Thread Duy Nguyen
On Thu, Feb 25, 2016 at 6:23 AM, Junio C Hamano wrote: > Thinking about it more, I have to say that I do not agree with the > basic premise of this patch. I-T-A is not "may want to commit, but > they are untracked" at all. It is "I know I want to add, I just > cannot yet decide the exact content

Re: [PATCH] unpack-trees: do not delete i-t-a entries in worktree even when forced

2016-02-24 Thread Junio C Hamano
Junio C Hamano writes: > Nguyễn Thái Ngọc Duy writes: > >> Intent-to-add entries are basically "I may want to commit these files >> later, but for now they are untracked". As such, when the user does "git >> reset --hard ", which removes i-t-a entries from the index, i-t-a >> entries in worktre

Re: [PATCH] unpack-trees: do not delete i-t-a entries in worktree even when forced

2016-02-24 Thread Junio C Hamano
Nguyễn Thái Ngọc Duy writes: > Intent-to-add entries are basically "I may want to commit these files > later, but for now they are untracked". As such, when the user does "git > reset --hard ", which removes i-t-a entries from the index, i-t-a > entries in worktree should be kept as untracked.

[PATCH] unpack-trees: do not delete i-t-a entries in worktree even when forced

2016-02-24 Thread Nguyễn Thái Ngọc Duy
Intent-to-add entries are basically "I may want to commit these files later, but for now they are untracked". As such, when the user does "git reset --hard ", which removes i-t-a entries from the index, i-t-a entries in worktree should be kept as untracked. Signed-off-by: Nguyễn Thái Ngọc Duy ---