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 781787 - Schema org.gnome.Calendar.json shall not have comments
Schema org.gnome.Calendar.json shall not have comments
Status: RESOLVED FIXED
Product: gnome-calendar
Classification: Applications
Component: General
3.24.x
Other Linux
: Normal minor
: 3.26
Assigned To: GNOME Calendar maintainers
GNOME Calendar maintainers
Depends on:
Blocks:
 
 
Reported: 2017-04-26 17:31 UTC by clobrano
Modified: 2017-05-13 16:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to remove comments from json file (1.31 KB, patch)
2017-04-26 17:31 UTC, clobrano
none Details | Review
Patch v2 (1.33 KB, patch)
2017-04-26 20:07 UTC, clobrano
none Details | Review
Patch v3 (1.59 KB, patch)
2017-04-27 17:04 UTC, clobrano
accepted-commit_now Details | Review

Description clobrano 2017-04-26 17:31:13 UTC
Created attachment 350498 [details] [review]
Patch to remove comments from json file

As per subject, org.gnome.Calendar.json schema has comments in C-style that are not allowed in a json file.
Comment 1 Carlos Soriano 2017-04-26 18:18:45 UTC
Review of attachment 350498 [details] [review]:

Code looks good, the commit message doesn't follow the guidelines though. You can read them in the newcomers wiki
Comment 2 clobrano 2017-04-26 20:07:43 UTC
Created attachment 350504 [details] [review]
Patch v2

Fixed patch according to previous comment, should be good now. Sorry for the mistake
Comment 3 Carlos Soriano 2017-04-27 13:45:35 UTC
Review of attachment 350504 [details] [review]:

Heya, thansk for the update.
The commit message is still missing a description, did you read the guidelines we provide?
Comment 4 clobrano 2017-04-27 13:59:30 UTC
That's weird. I do remember the full description inside my commit, something must have gone wrong somehow. I'll update it again in a couple of hours.
Comment 5 Carlos Soriano 2017-04-27 14:04:47 UTC
did you use git format-patch -1? that should work
Make sure you are not in "rebase" or something (you are not if you don't know what is this :D)
Comment 6 clobrano 2017-04-27 14:10:52 UTC
No, I didn't rebase, I just amended the previous commit :)
I used gitg this time, but something was already not right because it wasn't able to grab name and email from its own configuration and I had to fix it myself in the patch.
I'll be back to git format-patch which I know better :D
Comment 7 Carlos Soriano 2017-04-27 14:12:35 UTC
Indeed, I forgot to mention seems there is a bug in gitg about that. :( so yeah, git format-patch, sorry!
Comment 8 clobrano 2017-04-27 17:04:03 UTC
Created attachment 350565 [details] [review]
Patch v3
Comment 9 clobrano 2017-04-27 17:05:00 UTC
(In reply to Carlos Soriano from comment #7)
> Indeed, I forgot to mention seems there is a bug in gitg about that. :( so
> yeah, git format-patch, sorry!

No worries :)
I've never struggle this much with a so easy patch :D
Hope this is fine ;)
Comment 10 Carlos Soriano 2017-04-28 07:48:41 UTC
Review of attachment 350565 [details] [review]:

now looks good, thanks for the patch!
Comment 11 clobrano 2017-04-28 09:04:59 UTC
Great! Thanks
Comment 12 clobrano 2017-05-13 06:51:32 UTC
Just for curiosity, what's the process to have it in master branch?

Thanks
Comment 13 Carlos Soriano 2017-05-13 07:11:55 UTC
Whops, the process is someone commiting it, but I forgot :)

Now is in master, congrats!!
Comment 14 clobrano 2017-05-13 16:25:13 UTC
:D thank you!