{"thread":{"id":"10888","subject":"Re: core.excludesfile clean-up","startedAt":"2007-11-15T14:16:21Z","lastAt":"2007-11-15T14:16:21Z","messageCount":1,"participants":["Johannes Sixt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"59986","messageId":"473C54B5.5060500@viscovery.net","threadId":"10888","inReplyTo":null,"subject":"Re: core.excludesfile clean-up","fromName":"Johannes Sixt","fromEmail":"j.sixt@viscovery.net","sentAt":"2007-11-15T14:16:21Z","receivedAt":"2007-11-15T14:16:21Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Junio,\n\nin 039bc64e886 core.excludesfile clean-up you wrote:\n\n > We probably could change git-ls-files to use the standard set\n > when no excludes are specified on the command line and ignore\n > processing was asked, or something like that, but that will be a\n > change in semantics and might break people's scripts in a subtle\n > way.  I am somewhat reluctant to make such a change.\n\nJust for the records: git-filter-branch uses git-ls-files in a way that \nrequires that no exclude files are in effect. In particular, if the tree \nfilter creates new files, they are unconditionally added. See the \ndocumentation of --tree-filter.\n\n-- Hannes\n"}]}