Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gitignore: Add cscope files #173

Closed
wants to merge 1 commit into from
Closed

gitignore: Add cscope files #173

wants to merge 1 commit into from

Conversation

vkochan
Copy link
Contributor

@vkochan vkochan commented Oct 21, 2014

No description provided.

@b4n
Copy link
Member

b4n commented Oct 21, 2014

Why? Do something in the build system or alike generate them?

@frlan
Copy link
Member

frlan commented Oct 21, 2014

Seems to be a common tool in real world. I've just cherry-picked it as it doesn't hurt

@frlan frlan closed this Oct 21, 2014
@b4n
Copy link
Member

b4n commented Oct 21, 2014

I don't think we should add everything to our .gitignore just because it's "common". If some tools spurt out files everywhere and the user cares, he has several means for achieving the exact same goal without convincing every upstream project to add a new ignore rule. One of these solutions is to add such rules in ~/.gitignore. Another is to list those in .git/info/exclude.

So although I don't mind much, I woulnd't have merged this kind of things without sensible reason.

@frlan
Copy link
Member

frlan commented Oct 21, 2014

Well, fair point. Will leave this in, but for future request you might true.

@codebrainz
Copy link
Member

In the future we could also consider using .gitignore files in each plugin's directory and leaving the root one for global Autotools and Waf cruft.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants