After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 687930 - g-o-a has autogenerated .gitignore in version control
g-o-a has autogenerated .gitignore in version control
Status: RESOLVED FIXED
Product: gnome-online-accounts
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: GNOME Online Accounts maintainer(s)
GNOME Online Accounts maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-11-08 16:22 UTC by Allison Karlitskaya (desrt)
Modified: 2012-11-09 11:04 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
.gitignore is autogenerated, remove it from version control (1.19 KB, patch)
2012-11-08 22:57 UTC, Debarshi Ray 		committed Details | Review

Description Allison Karlitskaya (desrt) 2012-11-08 16:22:13 UTC 
git.mk is in use but .gitignore is stored in version control.  This is causing spurious diffs.
Comment 1 Allison Karlitskaya (desrt) 2012-11-08 16:26:20 UTC 
Note: this is kinda annoying because it makes jhbuild think that the module needs to be rebuilt, which also forces rebuilds of evolution-data-server, evolution, etc...
Comment 2 Debarshi Ray 2012-11-08 17:39:22 UTC 
Is it just about removing (git rm) it from the version control? I do not know the details of git.mk.
Comment 3 Allison Karlitskaya (desrt) 2012-11-08 20:12:51 UTC 
Yes.
Comment 4 Debarshi Ray 2012-11-08 22:57:25 UTC 
Created attachment 228516 [details] [review]
.gitignore is autogenerated, remove it from version control

The autogenerated .gitignore does not have the ignore rules for all these gdbus-codegen generated XML files among other things. How do I teach git.mk to take care of them?

Anyway, here is the patch that removes it from version control.
Comment 5 Debarshi Ray 2012-11-09 11:04:35 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.