All of lore.kernel.org
 help / color / mirror / Atom feed
From: wkevils@gmail.com (Kevin Wilson)
To: kernelnewbies@lists.kernelnewbies.org
Subject: minimum commit id length when fixing a patch
Date: Tue, 6 Jun 2017 23:34:33 +0300	[thread overview]
Message-ID: <CAGXs5wVfjYD-ETJ-v74MBbqifTOP9sMiW7B93EWuf+gGWA_2UQ@mail.gmail.com> (raw)

Hi,
I want to send a patch to LKML fixing something wrong which was caused
by other patch.

Form what I understand, it is a good practice to mention the commit
title and the commit ID.

A commit ID is very long. My question is: when mentioning in my commit
log the patch that caused the problem, what is the minimum commit id
length which I should use when presenting the patch that caused the
problem ? is such commit length is documented anywhere ?

Regards,
Kevin

             reply	other threads:[~2017-06-06 20:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 20:34 Kevin Wilson [this message]
2017-06-06 20:55 ` minimum commit id length when fixing a patch Leo Silva (a.k.a kirotawa)
2017-06-06 20:57 ` Bjørn Mork
2017-06-08 10:29   ` Kevin Wilson
2017-06-08 10:46     ` Bjørn Mork
2017-06-08 11:58       ` Kevin Wilson
2017-06-08 12:31         ` Bjørn Mork
2017-06-06 21:03 ` Igor Pylypiv

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGXs5wVfjYD-ETJ-v74MBbqifTOP9sMiW7B93EWuf+gGWA_2UQ@mail.gmail.com \
    --to=wkevils@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.