<html>
    <head>
      <base href="https://bugzilla.gnome.org/" />
    </head>
    <body><span class="vcard"><a href="page.cgi?id=describeuser.html&login=otaylor%40redhat.com" title="Owen Taylor <otaylor@redhat.com>"> <span class="fn">Owen Taylor</span></a>
</span> changed
              <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Wrong (ultra tiny/small) cursor size on HiDPI screen"
   href="https://bugzilla.gnome.org/show_bug.cgi?id=744932">bug 744932</a>
          <br>
             <table border="1" cellspacing="0" cellpadding="8">
          <tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right;">Attachment #299281 status</td>
           <td>none
           </td>
           <td>reviewed
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Wrong (ultra tiny/small) cursor size on HiDPI screen"
   href="https://bugzilla.gnome.org/show_bug.cgi?id=744932#c29">Comment # 29</a>
              on <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Wrong (ultra tiny/small) cursor size on HiDPI screen"
   href="https://bugzilla.gnome.org/show_bug.cgi?id=744932">bug 744932</a>
              from <span class="vcard"><a href="page.cgi?id=describeuser.html&login=otaylor%40redhat.com" title="Owen Taylor <otaylor@redhat.com>"> <span class="fn">Owen Taylor</span></a>
</span></b>
        <pre>Review of <span class=""><a href="attachment.cgi?id=299281&action=diff" name="attach_299281" title="Move meta-cursor-* files to new frontends/ directory">attachment 299281</a> <a href="attachment.cgi?id=299281&action=edit" title="Move meta-cursor-* files to new frontends/ directory">[details]</a></span> <a href='review?bug=744932&attachment=299281'>[review]</a>:

Hmm, in the context of trying to get 3.16.x working well in a hidpi
environment, this seems like it's a bit of an extraneous refactor. 

I dislike the frontends/ naming - I think it's "clever" rather than informative
rather than informative. There's a pretty well established idea that the
"frontend" of a system is on the user-facing side
(<a href="http://en.wikipedia.org/wiki/Front_and_back_ends">http://en.wikipedia.org/wiki/Front_and_back_ends</a>), so I think people are not
going to look in a frontends/ directory for the code relating to protocols. I
think this would be better called protocols/.

>From IRC <Jasper> And protocol/ could easily get confused with the Wayland
protocol .xml files.

Still, I think that's a minor confusion that will quickly go away when someone
looks inside the directory, as opposed to something that has to be explained to
people before it makes any sense.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are on the CC list for the bug.</li>
      </ul>
    </body>
</html>