From: Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Quick question
Date: Mon, 13 Feb 2006 19:26:03 +0100 [thread overview]
Message-ID: <43F0CF3B.6040807@gorzow.mm.pl> (raw)
In-Reply-To: <Pine.LNX.4.64.0602130848220.3691@g5.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
Linus Torvalds wrote:
>
> Well, since you're telling it to only show excluded files, it will also
> only show excluded directories.
>
> Which is admittedly insane. You don't want to exclude directories. Or
> maybe you do, but then we should add the "/" to the end before we do the
> exclusion.
>
> This patch (untested) will never exclude directories. Which may or may not
> be the right thing.
>
> Junio? Others? Comments?
>
For me it seems to do the right thing, although I have no need to exclude directories.
If I really needed to, I'd say something like:
/excluded_dir/*
in .git/info/exclude, and it would show the files as being excluded.
--
GPG Key id: 0xD1F10BA2
Fingerprint: 96E2 304A B9C4 949A 10A0 9105 9543 0453 D1F1 0BA2
AstralStorm
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2006-02-13 18:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 16:36 Quick question Radoslaw Szkodzinski
2006-02-13 16:54 ` Linus Torvalds
2006-02-13 18:26 ` Radoslaw Szkodzinski [this message]
2006-02-13 20:17 ` Alex Riesen
2006-02-14 7:52 ` Junio C Hamano
2006-02-14 0:40 ` Junio C Hamano
2006-02-14 1:50 ` Radoslaw Szkodzinski
2006-02-14 2:03 ` Junio C Hamano
2006-02-14 2:21 ` Radoslaw Szkodzinski
-- strict thread matches above, loose matches on Subject: below --
2012-03-01 19:00 Quick Question Max Lucchetti
2012-03-01 19:35 ` Junio C Hamano
2012-03-01 19:45 ` Max Lucchetti
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=43F0CF3B.6040807@gorzow.mm.pl \
--to=astralstorm@gorzow.mm.pl \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).