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 611658 - Update documentation for gtkvscrollbar
Update documentation for gtkvscrollbar
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Documentation
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 599599
 
 
Reported: 2010-03-03 00:39 UTC by Steven Harms
Modified: 2010-03-04 01:36 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Update documentation for gtkvscrollbar (2.99 KB, patch)
2010-03-03 00:39 UTC, Steven Harms 		needs-work Details | Review
Update documentation for gtkvscrollbar (3.06 KB, patch)
2010-03-03 23:27 UTC, Steven Harms 		none Details | Review
Update documentation for gtkvscrollbar (3.05 KB, patch)
2010-03-03 23:41 UTC, Steven Harms 		committed Details | Review

Description Steven Harms 2010-03-03 00:39:54 UTC 
Created attachment 155094 [details] [review]
Update documentation for gtkvscrollbar

Update documentation per http://live.gnome.org/GTK+/TaskAPIDocMigration
Comment 1 Javier Jardón (IRC: jjardon) 2010-03-03 02:25:51 UTC 
Review of attachment 155094 [details] [review]:

Please, remove the trailing whitespaces

Otherwise looks good, thank you
Comment 2 Steven Harms 2010-03-03 23:27:24 UTC 
Created attachment 155178 [details] [review]
Update documentation for gtkvscrollbar

Updated, removing trailing whitespace
Comment 3 Steven Harms 2010-03-03 23:41:07 UTC 
Created attachment 155181 [details] [review]
Update documentation for gtkvscrollbar

Fixed email
Comment 4 Javier Jardón (IRC: jjardon) 2010-03-04 01:35:31 UTC 
Comment on attachment 155181 [details] [review]
Update documentation for gtkvscrollbar

I've modified the commit message a bit to follow the same structure than previous patches

commit f0f3b01876a8cb3d905ae472ab55ca2b68a8913e
Comment 5 Javier Jardón (IRC: jjardon) 2010-03-04 01:36:03 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release.

Thank you Steven.