Re: [RFA] .gitignore: Ignore *.pyc files.
Ping. This patch seems fairly straightforward to the point of being almost obvious, but so far, no review (beyond one email expressing interest). Thanks! The GDB sources contain some python files, and executing them causes these .pyc files to appear. We could ignore them in GDB only, but I think this is the type of extension (compilation artifact) which can be shared amoung all projects. ChangeLog: * .gitignore: Ignore *.pyc file. Ok to apply? Thanks, -- Joel --- .gitignore |1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index dc1bf3f..8e2e1e9 100644 --- a/.gitignore +++ b/.gitignore @@ -12,6 +12,7 @@ *.la *.lo *.o +*.pyc *.tmp .deps -- 1.7.10.4 -- Joel
[RFA] .gitignore: Ignore *.pyc files.
Hello, The GDB sources contain some python files, and executing them causes these .pyc files to appear. We could ignore them in GDB only, but I think this is the type of extension (compilation artifact) which can be shared amoung all projects. ChangeLog: * .gitignore: Ignore *.pyc file. Ok to apply? Thanks, -- Joel --- .gitignore |1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index dc1bf3f..8e2e1e9 100644 --- a/.gitignore +++ b/.gitignore @@ -12,6 +12,7 @@ *.la *.lo *.o +*.pyc *.tmp .deps -- 1.7.10.4
Re: [RFA] .gitignore: Ignore *.pyc files.
On Dec 7, 2012, at 1:36 AM, Joel Brobecker brobec...@adacore.com wrote: The GDB sources contain some python files, and executing them causes these .pyc files to appear. We could ignore them in GDB only, but I think this is the type of extension (compilation artifact) which can be shared amoung all projects. This happened to us in a gcc port, so, we'd like this… Don't know if anyone else cares enough to say ok however. I might ask objections?