Re: bug report on update-index --assume-unchanged

From: Sérgio Basto <sergio@serjux.com>
Date: Dec 6, 2014, 00:45 UTC
Message-ID: <1417826757.30899.16.camel@segulix>
In-Reply-To: <12536C063959480083CC2D4CBA0BA38E@PhilipOakley>

On Sex, 2014-12-05 at 20:48 +0000, Philip Oakley wrote:

Show 12 quoted lines

> The problem here is that there is no guidance on what those actions
> are
> that may make git 'notice'. The man page git-update-index isn't as
> clear
> as it could be. Using --really-refresh being one option that would
> make
> git notice, but I wouldn't know when that is used.
> 
> Part of the implied question is why "git commit ." would notice when
> when "git commit -a" didn't appear to. So it's unclear as to what the 
> user should have expected.
>

I agree with this sentence, this is a bug because:

git commit -a ( and -a means all ) is incoherent with "git commit ." This is stupid because when I want commit part of the tree, commit includes one file that is not included when I say to commit all . So maybe you should fix, git commit -a to be coherent .

> (Note, I don't use assume-unchanged myself so this is more about 
> supporting the user/manual clarification. It is mentioned moderately 
> often on stackoverflow etc.)

yeap

Sorry I don't have time to read all messages in thread , but I'm going to test git with the patch suggest in this thread , at least, I solve "my" problem for some time ...

Thanks,

-- 
Sérgio M. B.