From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>, Catalin Marinas <catalin.marinas@gmail.com>
Cc: Pierre Ossman <drzeus-list@drzeus.cx>, git@vger.kernel.org
Subject: Re: Git and cogito uses different exclude files
Date: Fri, 16 Sep 2005 09:43:27 -0700 [thread overview]
Message-ID: <7vfys5ote8.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050916104430.GA25169@pasky.or.cz> (Petr Baudis's message of "Fri, 16 Sep 2005 12:44:30 +0200")
Petr Baudis <pasky@suse.cz> writes:
>> 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.
next prev parent reply other threads:[~2005-09-16 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 7:49 Git and cogito uses different exclude files Pierre Ossman
2005-09-16 8:34 ` Catalin Marinas
2005-09-16 10:44 ` Petr Baudis
2005-09-16 16:43 ` Junio C Hamano [this message]
2005-09-17 5:50 ` Petr Baudis
2005-09-17 6:45 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vfys5ote8.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=catalin.marinas@gmail.com \
--cc=drzeus-list@drzeus.cx \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).