From: Zé <jose.passes@gmx.com>
To: unlisted-recipients:; (no To-header on input)
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: gitignore vs. exclude vs assume-unchanged?
Date: Sat, 26 Apr 2014 13:26:12 +0100 [thread overview]
Message-ID: <535BA5E4.5050609@gmx.com> (raw)
In-Reply-To: <xmqqtx9l5jxn.fsf@gitster.dls.corp.google.com>
On 04/22/2014 06:54 PM, Junio C Hamano wrote:
> Interesting. It will break immediately when the project starts
> wanting to distribute its "canonical" ignore list
If that happens, that's a problem caused by the project wanting to
misuse .gitignore.
There are good practices and bad practices. Forcing a common .gitignore
upon everyone with access to the source code is not a good practice.
--
Zé
prev parent reply other threads:[~2014-04-26 12:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 16:33 gitignore vs. exclude vs assume-unchanged? alex
2014-04-16 17:51 ` Junio C Hamano
2014-04-16 23:07 ` alex
2014-04-16 23:45 ` Jonathan Nieder
2014-04-18 0:36 ` alex
2014-04-22 0:40 ` Andrew Ardill
2014-04-22 17:54 ` Junio C Hamano
2014-04-25 23:09 ` alex
2014-04-26 7:52 ` luc.linux
2014-04-26 12:26 ` Zé [this message]
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=535BA5E4.5050609@gmx.com \
--to=jose.passes@gmx.com \
--cc=git@vger.kernel.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).