From: Junio C Hamano <junkio@cox.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Clarified documentation of --exclude-per-directory.
Date: Mon, 25 Sep 2006 22:11:07 -0700 [thread overview]
Message-ID: <7v3baftdp0.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060925155821.GC26844@spearce.org> (Shawn Pearce's message of "Mon, 25 Sep 2006 11:58:21 -0400")
Shawn Pearce <spearce@spearce.org> writes:
> Tommi Virtanen noted on #git today that
>
> git ls-files --exclude-per-directory
>
> doesn't appear to work as advertised by the documentation unless
> --others is also used. According to the current source code this
> is the case as the --exclude-per-directory file isn't read unless
> we are iterating over the working directory, which only happens
> with --others.
I am puzzled by this problem description.
If we _were_ to read --exclude-per-directory file when we are
not doing --others, what better behaviour would we get out of
the command?
next prev parent reply other threads:[~2006-09-26 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 15:58 [PATCH] Clarified documentation of --exclude-per-directory Shawn Pearce
2006-09-26 5:11 ` Junio C Hamano [this message]
2006-09-26 21:41 ` Shawn Pearce
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=7v3baftdp0.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).