Re: Git and cogito uses different exclude files
- From
Junio C Hamano <junkio@cox.net>
- Date
- Sep 16, 2005, 16:43 UTC
- Message-ID
- <7vfys5ote8.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <20050916104430.GA25169@pasky.or.cz>
Petr Baudis <pasky@suse.cz> writes:
Show 5 quoted lines
>> The latest StGIT snapshot uses .git/info/exclude. Probably next week I >> will make a new StGIT release. > > So does Cogito now. ;-) It still looks at .git/exclude as well and gives > warning if it exists.
Late last night I could not find in the list archive the "list consensus" I used to justify what 'git-status' does in this log message:
Message-ID: <7vfysw89do.fsf@assigned-by-dhcp.cox.net>
From: Junio C Hamano <junkio@cox.net>
Subject: [PATCH] Teach git-status-script about git-ls-files --others
Date: Fri, 26 Aug 2005 18:18:59 -0700 When there is non-empty $GIT_DIR/info/exclude file, use it along
with .gitignore per-directory exclude pattern files (which was
a convention agreed on the list while ago and is compatible with
Cogito) to generate a list of ignored files as well.Signed-off-by: Junio C Hamano <junkio@cox.net>
I do remember checking Cogito and StGIT and making sure the use of .gitignore is consistent with you two, but I do not remember if we had consensus on info/exclude now. It could be that I was just hallucinating back then and ended up forcing this change onto you and your users by mistake in this round.
Anyway, thanks both.