From: Yohei Endo <yoheie@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Wrong gitignore precedence?
Date: Thu, 23 Apr 2015 21:11:52 +0900 [thread overview]
Message-ID: <20150423211152.0fdcbd2cdb48c98d15fe446c@gmail.com> (raw)
In-Reply-To: <xmqqh9s8dm6f.fsf@gitster.dls.corp.google.com>
On Wed, 22 Apr 2015 11:59:04 -0700
Junio C Hamano <gitster@pobox.com> wrote:
> Swapping the order in the code this late in the game after 8 years
> may affect people who have come to rely on the current behaviour and
> never read the doc, which is somewhat worrying, though.
I agree. I think the change should be well announced before
the fix is applied, like when the implicit value of
push.default was changed.
Thanks.
--
遠藤 陽平 (Yohei Endo)
yoheie@gmail.com
next prev parent reply other threads:[~2015-04-23 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 6:05 Wrong gitignore precedence? Yohei Endo
2015-04-22 18:59 ` Junio C Hamano
2015-04-23 12:11 ` Yohei Endo [this message]
2015-04-22 21:39 ` [PATCH] ignore: info/exclude should trump core.excludesfile Junio C Hamano
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=20150423211152.0fdcbd2cdb48c98d15fe446c@gmail.com \
--to=yoheie@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).