<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Unknown Card-Ids (3371|1019|2125), Chipset: P4M900/VN896/CN896"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94130#c21">Comment # 21</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Unknown Card-Ids (3371|1019|2125), Chipset: P4M900/VN896/CN896"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94130">bug 94130</a>
from <span class="vcard"><a class="email" href="mailto:huangran@iscas.ac.cn" title="HuangRan <huangran@iscas.ac.cn>"> <span class="fn">HuangRan</span></a>
</span></b>
<pre>(In reply to Benno Schulenberg from <a href="show_bug.cgi?id=94130#c19">comment #19</a>)
<span class="quote">> (In reply to Kevin Brace from <a href="show_bug.cgi?id=94130#c14">comment #14</a>)
> > I can go with the idea of releasing OpenChrome Version 0.3.4, but I will say
> > that I will need to reverse last several commits I have made.
>
> There is no need to reverse or revert any commits. Just create a new branch
> from just before you made the big removals, like I suggested. This way you
> avoid an unneeded reversal and then later reapplying of these changes -- it
> will look real ugly in git history.</span >
Yup, Benno, actually right now when I worked on OpenChrome DRM/DDX code, I use
a branch to do that and create patch for us to discuss, then if that is fine
for all of us, we can make it merged into master.
Thanks,
Frank</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>