Re: [PATCH v2] doc: make clear --assume-unchanged's user contract

2014-12-09 Thread Sérgio Basto
On Ter, 2014-12-09 at 16:44 -0800, Junio C Hamano wrote: > Sérgio Basto writes: > > > Also don't understand why --assumed-untracked shouldn't deal with > > changed files instead fallback in "the user promises not to change the > > file" and sometime

Re: [PATCH v2] doc: make clear --assume-unchanged's user contract

2014-12-08 Thread Sérgio Basto
On Sáb, 2014-12-06 at 15:04 +, Philip Oakley wrote: > Many users misunderstand the --assume-unchanged contract, believing > it means Git won't look at the flagged file. > > Be explicit that the --assume-unchanged contract is by the user that > they will NOT change the file so that Git does no

Re: [PATCH] commit: ignore assume-unchanged files in "commmit " mode

2014-12-08 Thread Sérgio Basto
On Sex, 2014-12-05 at 17:56 +0700, Nguyễn Thái Ngọc Duy wrote: > In the same spirit of 7fce6e3 (commit: correctly respect skip-worktree > bit - 2009-12-14), if a file is marked unchanged, skip it. > > Noticed-by: Sérgio Basto > Signed-off-by: Nguyễn Thái Ngọc Duy > --- &

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

2014-12-05 Thread Sérgio Basto
On Sex, 2014-12-05 at 20:48 +, Philip Oakley wrote: > 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,

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

2014-12-05 Thread Sérgio Basto
On Sex, 2014-12-05 at 10:30 -0800, Junio C Hamano wrote: > Your promise is "these paths I will not modify" and in return you > gain performance in "git status" yeah so --assume-unchanged is for administrators of git , like I write I change first and --assume-unchanged after and never change it

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

2014-12-05 Thread Sérgio Basto
Hi, On Sex, 2014-12-05 at 17:52 +0700, Duy Nguyen wrote: > On Fri, Dec 5, 2014 at 1:55 PM, Johannes Sixt wrote: > > Actually, it's a user error. When you set --assume-unchanged, then you give > > a promise to git that you do not change the files, and git does not have to > > check itself whether

bug report on update-index --assume-unchanged

2014-12-04 Thread Sérgio Basto
Hi, I add 2 files that I want ignore on commits git update-index --assume-unchanged configurations/local.defs git update-index --assume-unchanged processor/default.defs git diff -a is clean git diff . is clean git commit -a nothing added to commit but git commit . # Changes to be committ

GIT: ignoring changes in tracked files and bug report

2014-12-04 Thread Sérgio Basto
Hi, I'm trying find a solution where I can change file in a devel environment , and not commit it into git . git update-index --assume-unchanged is one solution , not the best solution but one solution. I add 2 files that I want ignore on commits git update-index --assume-unchanged configu