View All Attachments for Bug 103853

Attachment #135678
My GPG Public key	application/pgp-keys	2017-11-23 01:02:15 UTC	1.69 KB	no flags	Details

Attachment cannot be viewed because its MIME type is not text/*, image/*, or application/vnd.mozilla.*. Download the attachment instead.

Attachment #135679
DMR SSH public key	text/plain	2017-11-23 01:04:35 UTC	814 bytes	no flags	Details

Attachment #135799
attachment-19926-0.html	text/html	2017-11-29 14:49:51 UTC	3.11 KB	no flags	Details

<div dir="auto"><div dir="auto">Understood.</div><div dir="auto"><br></div><div dir="auto">My mission statement and the rest will be clearly written with the first set of patches for my target platforms P4M900 (and AMD RS690, if still necessary) IGP chipsets.</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">Best,</div><div dir="auto"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Nov 29, 2017 01:55,  &lt;<a href="mailto:bugzilla-daemon@freedesktop.org">bugzilla-daemon@freedesktop.org</a>&gt; wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
    
      
    
    <div><span class="m_2779339248787811417vcard"><a class="m_2779339248787811417email" href="mailto:martin.peres@free.fr" title="Martin Peres &lt;martin.peres@free.fr&gt;" target="_blank"> <span class="m_2779339248787811417fn">Martin Peres</span></a>
</span> changed
          <a class="m_2779339248787811417bz_bug_link m_2779339248787811417bz_status_RESOLVED m_2779339248787811417bz_closed" title="RESOLVED INVALID - Asking for an account" href="https://bugs.freedesktop.org/show_bug.cgi?id=103853" target="_blank">bug 103853</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">Status</td>
           <td>NEW
           </td>
           <td>RESOLVED
           </td>
         </tr>

         <tr>
           <td style="text-align:right">Resolution</td>
           <td>---
           </td>
           <td>INVALID
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="m_2779339248787811417bz_bug_link m_2779339248787811417bz_status_RESOLVED m_2779339248787811417bz_closed" title="RESOLVED INVALID - Asking for an account" href="https://bugs.freedesktop.org/show_bug.cgi?id=103853#c7" target="_blank">Comment # 7</a>
              on <a class="m_2779339248787811417bz_bug_link m_2779339248787811417bz_status_RESOLVED m_2779339248787811417bz_closed" title="RESOLVED INVALID - Asking for an account" href="https://bugs.freedesktop.org/show_bug.cgi?id=103853" target="_blank">bug 103853</a>
              from <span class="m_2779339248787811417vcard"><a class="m_2779339248787811417email" href="mailto:martin.peres@free.fr" title="Martin Peres &lt;martin.peres@free.fr&gt;" target="_blank"> <span class="m_2779339248787811417fn">Martin Peres</span></a>
</span></b>
        <pre>Hi Dubravko,

We do not create accounts for contributors who have not contributed anything
yet. Please get familiar with the project, get some patches accepted, then
Kevin will have enough information to actually grant you the right to push to
the official repo.

Sorry this was not clear-enough in the instructions.

Martin</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You reported the bug.</li>
      </ul>
    </div>
</blockquote></div></div>

Attachment #135877
attachment-3655-0.html	text/html	2017-12-02 10:24:52 UTC	4.36 KB	no flags	Details

<div dir="auto">Awesome, thanks!Â </div><div class="gmail_extra"><br><div class="gmail_quote">On Dec 1, 2017 15:55,  &lt;<a href="mailto:bugzilla-daemon@freedesktop.org">bugzilla-daemon@freedesktop.org</a>&gt; wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
    
      
    
    <div>
      <p>
        <div>
            <b><a class="m_2067808661963161946bz_bug_link m_2067808661963161946bz_status_RESOLVED m_2067808661963161946bz_closed" title="RESOLVED INVALID - Asking for an account" href="https://bugs.freedesktop.org/show_bug.cgi?id=103853#c11" target="_blank">Comment # 11</a>
              on <a class="m_2067808661963161946bz_bug_link m_2067808661963161946bz_status_RESOLVED m_2067808661963161946bz_closed" title="RESOLVED INVALID - Asking for an account" href="https://bugs.freedesktop.org/show_bug.cgi?id=103853" target="_blank">bug 103853</a>
              from <span class="m_2067808661963161946vcard"><a class="m_2067808661963161946email" href="mailto:martin.peres@free.fr" title="Martin Peres &lt;martin.peres@free.fr&gt;" target="_blank"> <span class="m_2067808661963161946fn">Martin Peres</span></a>
</span></b>
        <pre>(In reply to Kevin Brace from <a href="https://bugs.freedesktop.org/show_bug.cgi?id=103853#c10" target="_blank">comment #10</a>)
<span class="m_2067808661963161946quote">&gt; (In reply to <a href="mailto:dubrovnikdreamcoder@gmail.com" target="_blank">dubrovnikdreamcoder@gmail.com</a> from <a href="https://bugs.freedesktop.org/show_bug.cgi?id=103853#c8" target="_blank">comment #8</a>)
&gt; &gt; 
&gt; 
&gt; Hi Mario,
&gt; 
&gt; &gt; Understood.
&gt; &gt; 
&gt; &gt; My mission statement and the rest will be clearly written with the first
&gt; &gt; set of patches for my target platforms P4M900 (and AMD RS690, if still
&gt; &gt; necessary) IGP chipsets.
&gt; &gt; 
&gt; &gt; 
&gt; &gt; Best,
&gt; &gt; 
&gt; &gt; 
&gt; 
&gt; You do not really need a mission statement, but you do need to pick an area
&gt; you will like to work on.
&gt; Working on 2D (EXA), 3D (Gallium3D), and video acceleration are the areas I
&gt; have not had the time to devote so far, so it is more available for other
&gt; contributors to explore.
&gt; Of course, all of these assume the use of still in development OpenChrome
&gt; DRM.
&gt; Many Linux distributions have dropped non-KMS (Kernel Mode Setting) DDX from
&gt; their default (automatic) installation when you install the OS (you can
&gt; still install them in many cases, but requires an additional package
&gt; installation), hence, getting OpenChrome DRM mainlined inside Linux kernel
&gt; tree is my No. 1 priority at this point.
&gt; The code to support EXA is in the DDX, but it is currently disabled when
&gt; OpenChrome DRM is in use.
&gt; I will also like to support 3D acceleration someday, and previous developer
&gt; (James Simmons) started very early work on it more than 2 years ago, but he
&gt; abandoned it shortly after.
&gt; 
&gt; <a href="https://cgit.freedesktop.org/openchrome/mesa-openchrome/log/" target="_blank">https://cgit.freedesktop.org/<wbr>openchrome/mesa-openchrome/<wbr>log/</a>
&gt; ?qt=author&amp;q=James+Simmons
&gt; 
&gt; We can take this conversation offline to openchrome-devel mailing list.
&gt; After you post one or two useful patches on the openchrome-devel mailing
&gt; list, I can recommend you to obtain OpenChrome upstream repository commit
&gt; privilege from an <a href="http://x.org" target="_blank">x.org</a> administrator.</span>

Please indeed move the discussion to emails, and not to this bug report.

<span class="m_2067808661963161946quote">&gt; I was able to get another developer to obtain commit privilege back in 2016,
&gt; so it is possible.
&gt; 
&gt; <a class="m_2067808661963161946bz_bug_link m_2067808661963161946bz_status_RESOLVED m_2067808661963161946bz_closed" title="RESOLVED FIXED - Apply the commit privilege for OpenChrome project(DRM/DDX/MESA)" href="https://bugs.freedesktop.org/show_bug.cgi?id=94853" target="_blank">https://bugs.freedesktop.org/<wbr>show_bug.cgi?id=94853</a></span>

Yes, just come back here whenever Kevin tells you you are ready ;)</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You reported the bug.</li>
      </ul>
    </div>
</blockquote></div></div>

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.