From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: core.excludesfile clean-up
Date: Thu, 15 Nov 2007 15:16:21 +0100 [thread overview]
Message-ID: <473C54B5.5060500@viscovery.net> (raw)
Junio,
in 039bc64e886 core.excludesfile clean-up you wrote:
> We probably could change git-ls-files to use the standard set
> when no excludes are specified on the command line and ignore
> processing was asked, or something like that, but that will be a
> change in semantics and might break people's scripts in a subtle
> way. I am somewhat reluctant to make such a change.
Just for the records: git-filter-branch uses git-ls-files in a way that
requires that no exclude files are in effect. In particular, if the tree
filter creates new files, they are unconditionally added. See the
documentation of --tree-filter.
-- Hannes
reply other threads:[~2007-11-15 14:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=473C54B5.5060500@viscovery.net \
--to=j.sixt@viscovery.net \
--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 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.