<div dir="ltr"><div>If you run git log --oneline, you will see a sha ID of this size: a83727c, by example. So, I think it's the minimum you can use.<br><br></div>[]'s<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 6, 2017 at 5:34 PM, Kevin Wilson <span dir="ltr"><<a href="mailto:wkevils@gmail.com" target="_blank">wkevils@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
I want to send a patch to LKML fixing something wrong which was caused<br>
by other patch.<br>
<br>
Form what I understand, it is a good practice to mention the commit<br>
title and the commit ID.<br>
<br>
A commit ID is very long. My question is: when mentioning in my commit<br>
log the patch that caused the problem, what is the minimum commit id<br>
length which I should use when presenting the patch that caused the<br>
problem ? is such commit length is documented anywhere ?<br>
<br>
Regards,<br>
Kevin<br>
<br>
______________________________<wbr>_________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.<wbr>org</a><br>
<a href="https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" rel="noreferrer" target="_blank">https://lists.kernelnewbies.<wbr>org/mailman/listinfo/<wbr>kernelnewbies</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><br>----------------------------------------------<br>Leônidas S. Barbosa (Kirotawa)<br>blog: <a href="http://corecode.wordpress.com" target="_blank">corecode.wordpress.com</a><br><br>"<span style="font-size:12.8px">"O que importa são os incontáveis pequenos atos de pessoas desconhecidas, que fundam as bases para os eventos significativos que se tornam história" - Howard Zinn</span></div></div></div>
</div>