Re: gitignore design

From: Jakub Narebski <jnareb@gmail.com>
Date: Jul 29, 2011, 21:39 UTC
Message-ID: <201107292339.51753.jnareb@gmail.com>
In-Reply-To: <4E32B637.1030201@viscovery.net>

On Fri, 29 Jul 2011, Johannes Sixt napisał:

> Am 7/29/2011 15:19, schrieb Jakub Narebski:

Show 14 quoted lines

> > Are you sure?  It seems to work as I thought it would.
> > [...]
> > Notice that change to 'bar' didn't get comitted.
> 
> Of course, it didn't get committed, you promised not to change it, so why
> should git commit it?
> 
> However, your example does not show the dangerous part. git-commit is not
> dangerous. But you might run into trouble when git has to merge content
> into the worktree or index; in this case, git may decide to just read the
> file instead of to unpack an object - assuming that the content on disk is
> identical to the unpacked object (it will do so because with
> --assume-unchanged you promised not to change the file). If you broke your
> promise, you get to what you deserve ;)

True, it is *assume-unchanged*, not ignore-changes bit; though the latter
would be also possible to implement, I think... but having some file not
changing and marking it as such for better performance is saner use case
than tracking some file but not really tracking it.

> No code reference, sorry, because I'm just parrotting what I've read
> elsewhere on the list, for example,
> http://thread.gmane.org/gmane.comp.version-control.git/146082/focus=146353

Well, there is hint that there might be problems, but not really says that they are, and where (if one is lying about assume unchanged by changing assume-unchanged file).

-- 
Jakub Narębski
Poland