[
https://issues.apache.org/jira/browse/SOLR-10713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017819#comment-16017819
]
Jason Gerlowski commented on SOLR-10713:
----------------------------------------
I'd contend the "nightmarish" description you gave above- a search for "git
files not tracked" or "git status missing files", or the command {{git status
-h}} is enough to get on the right track in this rare case.
Admittedly, someone with less git experience might choose different search
terms. So point taken; it can be unintuitive, and that's a bad thing.
I can/will narrow down the {{pid}} file path due to that concern. What would
you propose I do with the other file extensions (which aren't pin-able to a
specific directory the was pid files are)? Should I give up on having git hide
them by default?
> git should ignore common output files (*.pid, *.out)
> ----------------------------------------------------
>
> Key: SOLR-10713
> URL: https://issues.apache.org/jira/browse/SOLR-10713
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Build
> Reporter: Jason Gerlowski
> Priority: Trivial
> Attachments: SOLR-10713.patch, SOLR-10713.patch
>
>
> During the course of experimenting/testing Solr, it's common to accumulate a
> number of output files in the source checkout. Many of these are already
> ignored via the {{.gitignore}}. (For example, {{*.jar}} and {{*.log}} files
> are untracked currently)
> Some common output files aren't explicitly ignored by git though. I know
> this is true of {{*.pid}} and {{*.out}} files (such as those produced by
> running a standalone ZK).
> It'd be nice if we could update the {{.gitignore}} to explicitly ignore these
> filetypes by default.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
