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 740713 - Improve week view drawing code
Improve week view drawing code
Status: RESOLVED DUPLICATE of bug 733947
Product: gnome-calendar
Classification: Applications
Component: Views
unspecified
Other Linux
: Normal minor
: 3.26
Assigned To: GNOME Calendar maintainers
GNOME Calendar maintainers
Depends on:
Blocks:
 
 
Reported: 2014-11-25 23:02 UTC by Georges Basile Stavracas Neto
Modified: 2017-04-17 18:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Georges Basile Stavracas Neto 2014-11-25 23:02:21 UTC 
Special care for the all-day grid.
Comment 1 Georges Basile Stavracas Neto 2014-11-25 23:02:48 UTC 
Marking this bug as developer-only bug.
Comment 2 André Klapper 2014-11-26 11:04:27 UTC 
(In reply to comment #1)
> Marking this bug as developer-only bug.

Why did you hide this ticket from other people? Please elaborate.
Comment 3 Georges Basile Stavracas Neto 2014-11-26 11:07:48 UTC 
Because this is not a bug itself, but a tracker for any related patches.
Is there anything against restricting visibility of bugs? This particular bug can be marked as publicy visible without problems.
Comment 4 André Klapper 2014-11-26 15:16:54 UTC 
Please provide reasons why you want to restrict visibility of this ticket. Is there anything secret here? I don't see any good reasons why to hide visibility of tracking tickets either - free software and its planning should be open and free if there are no specific and good reasons.
Comment 5 Erick Perez Castellanos 2014-11-26 15:29:35 UTC 
Making it public again. I don't think there's a good reason for hiding a bug from the user.
Comment 6 Erick Perez Castellanos 2015-01-28 21:14:16 UTC 
Moving all the bugs related with improving week-view into a single one.

*** This bug has been marked as a duplicate of bug 733947 ***