From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Jan Larres <jan@majutsushi.net>, git@vger.kernel.org
Subject: Re: check-attr doesn't respect recursive definitions
Date: Tue, 02 Apr 2013 09:11:02 -0700 [thread overview]
Message-ID: <7vtxnogbft.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130402143130.GC23828@sigill.intra.peff.net> (Jeff King's message of "Tue, 2 Apr 2013 10:31:30 -0400")
Jeff King <peff@peff.net> writes:
> Yes, it is the expected behavior, though I cannot offhand think of
> anything that would break if we did apply it recursively.
Conceptually that breaks our brain. "All files in doc/ directories
are text" and "doc/ directory is text" are two different things, no?
next prev parent reply other threads:[~2013-04-02 16:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 9:45 check-attr doesn't respect recursive definitions Jan Larres
2013-04-02 14:31 ` Jeff King
2013-04-02 14:48 ` Jeff King
2013-04-02 16:11 ` Junio C Hamano [this message]
2013-04-02 16:30 ` Jeff King
2013-04-02 16:43 ` Junio C Hamano
2013-04-02 16:51 ` Jeff King
2013-04-02 17:15 ` Jeff King
2013-04-02 17:16 ` Junio C Hamano
2013-04-02 19:16 ` Jeff King
2013-04-03 10:05 ` Jan Larres
2013-04-05 2:09 ` Duy Nguyen
2013-04-05 12:04 ` Jan Larres
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=7vtxnogbft.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jan@majutsushi.net \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.