Perforce Software p4ideax


Share your Idea

Use this form to quickly share you idea with us. Remember, please keep it constructive.

Don't have an account? Sign up.

Make the ignore feature work out the box

Posted over 1 year ago by Golf Hotel
Idea Status: new

The p4ignore feature doesn't work out the box — you have to set an environment variable telling Perforce what filename rule lists will have. This makes it hard to share rules with other developers

It also means you can't hack on two projects with different names for the ignore lists.

Why not just work like Git, which takes rules from all files called `.gitignore`. Everyone can share rules just by committing them

http://stackoverflow.com/a/13126496/284795

3 Comments

Matt Attaway

Posted over 1 year ago

Strangely enough the reason we make it configurable is to support .gitignore files. A request we had during the design was tobe able to support Git ignore files in Perforce as well.

Still, I agree that a sensible default would make a lot of sense. People could always override the value.

Flag as inappropriate

Golf Hotel

Posted over 1 year ago

Hi Matt. That makes sense. Ok, so any solution mustn't break that popular use case.

What if? The convention for ignore files were specified by the *repository*, rather than the user. Then, the ignore files would work out the box for all contributors. And developers could happily hack on two repositories with different conventions.

But what about personal rules? They could go somewhere in the user's home folder, as with Git https://www.kernel.org/pub/software/scm/git/docs/gitignore.html

Flag as inappropriate

Golf Hotel

Posted over 1 year ago

But that's a big change.

A simple choice of default for the existing behaviour would solve my woes. I hack on precisely one repository. I want the rules I share to work out the box.

Flag as inappropriate