From: Junio C Hamano <junkio@cox.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>,
Christian Gierke <ch@gierke.de>,
Nico -telmich- Schottelius <nico-linux-git@schottelius.org>
Subject: Re: first impressions to git
Date: Sun, 18 Sep 2005 10:31:37 -0700 [thread overview]
Message-ID: <7vr7bm470m.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0509181201220.23242@iabervon.org> (Daniel Barkalow's message of "Sun, 18 Sep 2005 12:56:21 -0400 (EDT)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> We need to fix the error for trying to add a directory, and we should
> probably support it in "add".
Yup.
> Core git doesn't have a .git/info/excludes at all. (And, in general,
> .gitignore makes more sense, I think, because you usually want this to be
> version-controlled; but maybe there should be .git/info/excludes as a
> default for new directories?)
We by default install info/excludes disabled in a new repository
and 'git status' looks at it. What it _does_ not do is to use
any exclude patterns by default; if info/excludes is empty
(modulo '# comment' lines) it does not use .gitignore.
> ".git/remotes" is the current one; ".git/branches" is obsolete.
Perhaps deprecated but obsolete is too strong a word -- it still
is supported.
next prev parent reply other threads:[~2005-09-18 17:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 11:12 first impressions to git Nico -telmich- Schottelius
2005-09-18 14:54 ` Petr Baudis
[not found] ` <94fc236b050918073351075bb4@mail.gmail.com>
2005-09-18 21:18 ` Nico -telmich- Schottelius
2005-09-18 21:39 ` Kay Sievers
2005-09-18 22:09 ` Junio C Hamano
2005-09-18 22:11 ` Petr Baudis
2005-09-18 22:23 ` Junio C Hamano
2005-09-18 22:29 ` Linus Torvalds
2005-09-18 16:56 ` Daniel Barkalow
2005-09-18 17:31 ` Junio C Hamano [this message]
2005-09-19 19:14 ` Sven Verdoolaege
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=7vr7bm470m.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=barkalow@iabervon.org \
--cc=ch@gierke.de \
--cc=git@vger.kernel.org \
--cc=kay.sievers@vrfy.org \
--cc=nico-linux-git@schottelius.org \
/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).